Communication Center Errors
This API documents the 200 response for each operation. The API can return the following errors instead. Errors use the same envelope as a successful response, with status.status set to ERROR and the code in status.error_code.
Errors for all communication center endpoints
Error Code | Message |
|---|---|
| The signature or access key is missing or not valid. |
| The requested resource was not found. |
| Missing header org_id to complete authentication. |
| Contact Rapyd Client Support. |
| Internal error. Please contact Rapyd Client Support. |
Get all case communication threads
Error Code | Message |
|---|---|
| A query parameter is not valid. The code names the parameter. |
Get case communication thread
Error Code | Message |
|---|---|
| A query parameter is not valid. The code names the parameter. |
| The communication thread was not found. The request was rejected. Corrective action: For the |
| Explanation: The communication thread does not exist. |
Add message to case communication thread
Error Code | Message |
|---|---|
| A value is not valid. |
| Explanation: |
| The communication thread was not found. The request was rejected. Corrective action: For the |
| Explanation: The message could not be added to the thread. |
Upload file to communication center
Error Code | Message |
|---|---|
| The request tried to upload a file, but the file type was not supported. The request was rejected. Corrective action: Upload a file that is of a supported file type. |
| The request attempted to upload multiple document files, but it includes too many files. The request was rejected. Corrective action: Lower the number of files in the request and resend it. |
| The file size is too large. |
| The request attempted to upload a document, but the document's file name is too long. The request was rejected. Corrective action: Rename the file according to the length limitation. |
| Internal error upload file. Please contact Rapyd Client Support. |
Download file
Error Code | Message |
|---|---|
| The communication thread was not found. The request was rejected. Corrective action: For the |
| Explanation: The attachment could not be retrieved. |