Each API request you send generates a unique record token. This token is our internal identifier for your record and will be used in all future responses, including reports. It allows you to track individual records, especially in projects with multiple instances of the same phone number.
Fields
| Field | Type | Description |
|---|---|---|
| Token | guid | This is the unique ID in our system for your request. |
| Success | boolean | Did we successfully process this request? |
| ResponseCode | int | See “Response Codese” below for a brief description. |
| Message | string | A brief description of what happened. |
{
"Token": "27C3CF6D-5542-4106-AF37-BF16045D6535",
"Success": true,
"ResponseCode":1,
"Message":"Success"
}Response Codes
| Code(s) | Description |
|---|---|
| 0, 2, 11, 13, 20, 21 | An unknown error has occurred. |
| 1 | This request has been successfully processed. |
| 3 | The API token is invalid. |
| 4 | The API token is not authorized for this request. |
| 10 | Invalid data was provided. |
| 12 | The request error was not able to be logged. |
| 14 | The Record Disposition is missing. |
| 17 | The project source is paused. |
| 18 | The records Phone and DID are the same. |
| 22 | A duplicate of the record you are trying to insert already exists. |
| 23 | The Record you are trying to insert is mobile and is being rejected. |
| 24 | The Phone provided is an invalid device type. |
| 26 | The Record is rejected due to the CarrierId not being accepted on the project. |
| 27 | The Record you are trying to insert is a landline and is being rejected. |