|
200 OK
|
The request was successfully completed. The system returns a 200 status for a successful GET or POST method.
Action: Although you may receive a successful HTTP status code, the intended action may not have completed successfully for all records in the request body. Examine the response body to determine whether the action completed successfully for each record sent.
|
|
400 Bad Request
|
Cause: The system cannot fulfill the request due to incorrect syntax.
Related error code examples: INVALID_PARAMETER
Actions:
- View the response body details to see if there is additional information about the problem.
- Verify that the URL format and parameters are correct for the API call. Check whether there are required parameters and make sure they contain valid values.
- Verify that the header has the correct format.
- Verify that the request body is formatted correctly, if applicable.
|
|
401 Unauthorized
|
Cause: The system cannot fulfill the request because the user does not have sufficient access to perform the call.
Related error code examples: API_DISABLED_FOR_USER, INSUFFICIENT_ACCESS, API_LIMIT_EXCEEDED
Actions:
- View the response body details to see if there is additional information about the problem.
- Verify that the API user has the correct Roles assigned. You may need to ask the Responsys Account Administrator for assistance.
- Your API code may be attempting an API call that is not part of the standard Responsys API. View the Responsys documentation to verify whether the call is standard.
- For campaign-related APIs, ensure that your account is enabled for Email Message Designer (EMD) for email campaigns and Push for Push campaigns.
- For Email campaign-related APIs, ensure that the campaign that you are trying to use is not a "Classic" campaign.
|
|
404 Not Found
|
Cause: The system cannot find the item specified in the request.
Related error code examples: FOLDER_NOT_FOUND, DOCUMENT_NOT_FOUND, IMAGE_NOT_FOUND
Actions:
- View the response body detail to see if there is additional information about the problem. For example, for content library calls, it will show the document path in the request.
- For API calls that include path names, verify that the path exists in the system and that the parts of the path are spelled correctly.
- For image API calls/requests, examine the document file to ensure that the image tags are correct and to determine whether the document contains images.
|
|
405 Method Not Allowed
|
Cause: The method is incorrect for the endpoint you are using, or the endpoint format is incorrect for the method.
Related error code examples: METHOD_NOT_SUPPORTED
Actions:
- Verify that you have used the correct method and endpoint for the task you are trying to perform. For example, if you use the GET method to obtain a content library image but do not provide the complete path in the endpoint, you will see this error.
|
|
500 Internal Server Error
|
Cause: The server encountered an unexpected error that prevented it from fulfilling the request.
Related error code examples: UNEXPECTED_EXCEPTION, UNRECOVERABLE_EXCEPTION
Actions:
- View the response body to see if it provides additional information about the problem.
- Verify that you are using the correct endpoint for the correct request body. For example, if you use the old v1.1 endpoint with the new v1.3 request format, you will receive an internal server error.
- AFTM-enabled accounts only: If the error code is UNRECOVERABLE_EXCEPTION and your code is using AFTM supported APIs, re-log in and try the call or request again
|
|
503 Service Unavailable
|
Cause: The server is currently unable to handle the request, due to a temporary overloading or server maintenance.
Actions:
- View the response body to see if it provides additional information about the problem. For example, the response may return an HTML page informing you that the Responsys service is temporarily unavailable.
- Check the System Status blog page for your Responsys Interact environment to determine if there is system maintenance, and reschedule your API activity accordingly.
|