Troubleshooting & FAQ
API FAQs
How do you read API errors?
Each error contains three pieces of information separated by a | symbol:
- The first part is the row number in the CSV where the error occurred.
- The second part is the data value that caused the error.
- The third part is the error message.
Example error response:
I keep getting a 401 error. How do I resolve it?
A 401 error means the client ID, client secret, or bearer token you used is invalid. Copy the correct credentials from the Platform web app and try again.
If the problem persists after rechecking your credentials, try reloading the web app and copying the client secret again — your client ID will remain the same.
If it is still not resolved, contact support and include a raw trace of the request and response.
What is base64 encoding and how do I encode my credentials?
Base64 encoding converts binary data into a text string. You need to base64-encode the string <ClientID>:<URL_Encoded_ClientSecret> to form the value of your Authorization: Basic header.
Most API clients and platforms handle this automatically. If you need to do it manually, use an online tool such as base64encode.org.
Which authorization method should I use in the API reference?
The Platform uses OAuth 2.0 for authentication. When testing in the API reference documentation, use the OAuth2 option. Bearer and Basic authentication are simplified representations of the same flow.
The Basic auth option asks for a username and password — where do I enter my Client ID and Secret?
For Basic authorization, enter your Client ID as the username and your Client Secret as the password, as per the OpenAPI 3.0 specification.