Skip to main content

Troubleshooting 2205 – You Are Not Authorized

  • Updated

The 2205 – You are not authorized error indicates that the request could not be authenticated successfully. This is commonly caused by an incorrect API key, an invalid timestamp, or a signature mismatch.

Common Causes

Review the following requirements to identify the cause of the error.

1. Verify the API Key

Ensure you are using the correct API key for the environment you are accessing:

  • Sandbox endpoint: Use your Sandbox API key.
  • Production endpoint: Use your Production API key.

Using a key from one environment with an endpoint from another can result in a 2205 error.

2. Check the Timestamp Format

The timestamp must follow this format:

yyyy-MM-dd'T'HH:mm:ss.fffK

For example:

2026-08-11T09:30:00.000Z

Ensure the timestamp includes the required milliseconds and timezone information.

3. Use GMT (UTC+0)

The timestamp must be generated in GMT/UTC+0.

Do not use your local timezone when generating the timestamp. For example, if your application runs in a UTC+3 timezone, convert the timestamp to UTC before sending the request.

4. Ensure the Timestamp Matches the Signature

The timestamp included in the request must be exactly the same timestamp used when generating the signature.

For example:

Timestamp used in request:
2026-08-11T09:30:00.000Z

Timestamp used to generate signature:
2026-08-11T09:30:00.000Z

Even a small difference between the two timestamps can cause the signature validation to fail.

5. Generate a Fresh Signature for Every Request

A new signature should be generated for each API request.

Do not reuse a signature from a previous request, as signatures are tied to the request's authentication data and timestamp.

Troubleshooting Checklist

Before contacting Support, confirm that:

  • The API key matches the environment being used.
  • The timestamp follows yyyy-MM-dd'T'HH:mm:ss.fffK.
  • The timestamp is in GMT/UTC+0.
  • The timestamp in the request matches the timestamp used to generate the signature.
  • A fresh signature is generated for every request.

If you have confirmed all the above and are still receiving the 2205 – You are not authorized error, contact Support with the relevant request details so the issue can be investigated further.

Powered by Zendesk