Skip to content

Create an API key and troubleshoot access

Create a key through the account API area and diagnose access errors without exposing credentials.

Create a key for your integration

Sign in to TRAIEX, open Account → API and select New API. The official documentation states that the passphrase is displayed once. Store it securely when creating the key; do not include it in screenshots, logs or support requests.

For implementation and authentication details, follow the official API documentation. If the controls or access message differ, check the current account screen before proceeding.

1

Check the account and API area

Open the profile menu in the Exchange and select API. Confirm that you are viewing the intended account and read any status or access message shown there.

2

Record what failed

Note the action, response or error code, time and timezone. For an order or transfer request, check the corresponding operation history before retrying so a delayed response does not lead to a duplicate action.

3

Send a safe diagnostic description

Contact support with the failing action and a redacted request example if useful. Remove API keys, secrets, authorization headers, signatures and personal information before sharing logs or screenshots.

Before you continue

Do not grant broader access or share a secret to solve an error. If you believe credentials have been exposed, stop using them and report the suspected compromise through official support.

What to send support

Action or endpoint, error code and message, request time and timezone, relevant operation ID and a redacted example. Never include authentication material.

Contact support

Detailed product guide

Official TRAIEX API documentation

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article