Skip to content
ajar.Get started
Help center

Troubleshoot a rejected request

Check authentication, permissions, and request limits.

API keysUpdated 27 September 2026

401: authentication failed

Send the key in the Authorization header as Bearer followed by a space and the key. Check for a missing, expired, or revoked key. Do not use your dashboard session cookie as an API key.

403: access denied

Check the key’s scope and permission against the operation you are calling. Confirm that your account and workspace still have access. Signing in again will not change a key’s permissions.

429: request limit reached

Stop sending repeated requests. Check the limit and its period in the key’s settings. Wait for the period to reset, or ask a workspace owner to review the limit.

Report a failure

Include the operation, time and timezone, HTTP status, and request ID if one was returned. Remove the Authorization header and personal data before sharing a request or response.

Useful links

Check an API key · Sign in · Help center

Still need a hand?

Email us at contact@useajar.com.

Contact us