Troubleshooting

PubNub APIs return status codes for successful and unsuccessful operations. SDKs surface these codes, especially for errors. Handle errors in your client. Show a helpful message. Retry the operation when appropriate.

Refer to SDK troubleshooting and status event references below for links to SDK‑specific guidance.

HTTP status codes​

Each HTTP response includes a status code in the header:

  • 2xx or 3xx for success
  • 4xx or 5xx for failure

In addition to common codes (200 OK, 400 Bad Request, 404 Not Found), these less‑common codes may appear. Functions can return other codes; see your SDK’s reference for details.

CodeOperationDescription
207
Message Actions
The action was deleted but the action-deletion message wasn't published.
403
General
Not authorized. Verify Access Manager permissions for the key, or fix the generated signature.
412
App Context
Conditional operation can't be performed because the target object has changed since the last retrieval.
415
App Context
The format of the request body you supplied isn't supported. The request body must be in JSON format.
503
General
Request timed out. Retry with backoff. If the error persists, contact PubNub Support.

SDK troubleshooting and status event references​

Use these links to find SDK‑specific troubleshooting and status event references.

Last updated on
On this page