Skip to main content


Troubleshoot your Event API implementation by learning about associated errors.

Error table#

200Typically OK, but see example of a 200 error scenario below
400Malformed request
401Unauthorized or invalid authentication token
403Forbidden; authentication token does not grant operation on specified app_id.
409Idempotency token has been seen before.
500, 502, 503Unexpected errors on Rokt's end. Retry or contact your Rokt support team.


{    "data": [        "code": "400",        "message": "Malformed request"    ]}

200 error scenario#

HTTP Status 200 typically indicates a successful call. However, as the Event API is a batch API, a 200 response does not necessarily mean the whole request processed correctly. Developers should inspect the response payload to ensure all records have been processed. The response payload contains an error message as well as the specific event object that failed.

Level 1Level 2Level 3Level 4TypeDescription
unprocessedRecordsList[BulkResponseItemObject]A list of objects that contain records that failed to process.
errorErrorObjectDescribes the error related to the record.
codeStringError code
messageStringDetailed error message
recordEventObjectField contains the original record that failed.
{    "data": {        "unprocessedRecords": [            {                "error": {                    "code": "ValidationError",                        "message": "Invalid content"                },                "record": {                    "clientEventId": "fff4deeb-cdee-49ff-9aad-61b1c4256ca6",                    "eventType": "conversion",                    "eventTime": "2020-05-22T10:21:29.339Z",                    "objectData": [                        {                            "name": "firstname",                            "value": "john"                        }                    ]                }            }        ]    }}
Was this article helpful?