There is set of error codes that are returned by PubNub SDK when operations are unsuccessful. These codes should be handled on the client applications to display an error message to the user and to optionally retry the operation.
To find a list of PubNub events, refer to the Events page.
HTTP Error Codes
The success or failure of each HTTP request is shown in the status field of the HTTP response header, which contains standard HTTP status codes:
- a 2xx code for success
- a 4xx or 5xx code for failure
If the error message isn't clear, you may find information about the error by looking up the error code in the tables below.
|General||The REST call was successful. Refer to the detail usage by operation for more information on parsing the response.|
|General||The request body contains invalid parameters.|
|General||The client isn’t authorized to perform this operation. Either the authorization key you provided doesn’t have the required permissions for this operation, or the signature is invalid.|
|General||A resource with the given identifier already exists.|
|General||Request rate limit exceeded.|
|General||An internal server error occurred.|
|General||Request processing exceeded the maximum allowed time.|
|Objects||The requested object wasn't found.|
|Objects||Conditional operation can't be performed because the target object has changed since the last retrieval.|
|Objects||The format of the request body you supplied isn't supported. The request body must be in JSON format.|
|Message Actions||The action was deleted but the action-deletion message wasn't published.|
Here is a selected list of common client and server SDKs, with links to their troubleshooting and status event references. The documentation for each PubNub SDK includes a troubleshooting section detailing how to enable logging for that SDK, and a list of status events you may receive.