200 Success
The 200: Success status code indicates that the HTTP request was successful. In a GET
request, the response will contain an entity corresponding to the requested resource. In a POST
request, the response will contain an entity describing or containing the
result of the action.
Code | 200 |
---|---|
Description | Success. |
This is an example of a success message.
{
"pagination": {
"offset": 0,
"limit": 20,
"total": 1
},
"data": [
{
"projectId": "1234",
"projectName": "Top Secret Project",
"labels": {
"application": "Network Edge"
},
"parentOrganizationId": "1234",
"resourceSubType": "END_CUSTOMER",
"rootOrgId": "316.....",
"inboxResource": false,
"silentProject": false,
"permissions": [
{
"actions": [
"networkedge.acl.view",
"networkedge.acl.create",
"networkedge.acl.modify"
],
"resourceType": "ACL"
},
{
"actions": [
"fabric.port.read"
],
"resourceType": "PORT"
},
]
}
]
}
201 Success
The 201 (Success) status code indicates that the request has been fulfilled and has resulted in one or more new resources to be created.
Code | 201 |
---|---|
Description | Success. |
202 Success
The 202 (Success) status code indicates that the request has been received and getting processed for one or more existing resources to be updated or cancelled.
Code | 202 |
---|---|
Description | Success. |
202 Accepted
The 202: Accepted status code indicates that the request has been accepted for processing, but the processing has not been completed. Processing may not have started yet, the request might or might not be acted upon, and the request might be disallowed when processing actually takes place. In a PATCH
or POST
request, the response will contain an entity describing or containing the result of the action.
Code | 202 |
---|---|
Description | Accepted. |
This is an example of a success message.
{
"orderNumber": "1-126546546546"
}
204 No Content
The 204: No Content status code indicates that the server has successfully fulfilled the request and that there is no additional content to send in the response payload body. In a PATCH
or POST
request, the response will not contain a response payload body, but can return a HTTP header Location
containing the URL of the created resource.
Code | 204 |
---|---|
Description | No Content. |
This is an example of a successful HTTP header response.
Key | Value |
---|---|
Location | /tickets/1-211319530862 |