Troubleshooting tips
This topic contains tips for troubleshooting errors when using the Responsys APIs.
Catch and parse the full response payload
The full response payload provides both the HTTP status code and – in the case of error responses—the response body contains details about the error. Even in the case of a successful HTTP status code (200 OK), the response body may contain additional details about whether your request was successful for individual records sent.
What does a successful response mean?
For many of the APIs, a successful response means that the system has successfully received the data. However, for the APIs that trigger certain actions (such as triggerEmail, triggerPush, triggerSMS, triggerCustomEvent), the initial “success” response does not necessarily mean that the end action was completely successful.
- A success response in trigger custom event means that Responsys placed the recipients into the program, but it does not mean that the enactment has completed successfully.
- A successful response for the trigger or for merge & trigger APIs does not mean that the campaign was sent successfully to all recipients. In the following Merge Trigger SMS example, the first record was successfully merged and the SMS message was sent to the recipient whose RIID is 72067. The second record was successfully merged, but the SMS message was undeliverable.
[
{
"errorMessage": null,
"success": true,
"recipientId": 72067
},
{
"errorMessage": "RECIPIENT_STATUS_UNDELIVERABLE: Recipient deliverability status is undeliverable",
"success": false,
"recipientId": -1
}
]
Log your web service calls and payloads
We recommend that you log your web service calls and payloads, using a tool for that purpose (such as Log4J). The Responsys Web Services log has a 24-48 hour limit, depending on the traffic level. Keeping your own log will be helpful should you need to contact Oracle Support for help.