Troubleshooting
Learn how to resolve the most common problems people encounter in the REST API.
If you're encountering some oddities in the API, here's a list of resolutions to some of the problems you may be experiencing. If you have any problems or requests, please contact TextMaster support.
Not all results returned
Most API calls accessing a list of resources (e.g., abilities, projects, documents, etc.) support pagination. If you're making requests and receiving an incomplete set of results, you're probably only seeing the first page. You'll need to request the remaining pages in order to get more results.
OAuth Authentication errors
When exchanging a code for an access token, additional errors can occur. The format of these error responses is determined by the Accept
header you pass.
The examples below only show JSON responses.
Incorrect client credentials
If the client_id
and or client_secret
you pass are incorrect you will receive this error response:
To solve this error, make sure you have the correct credentials for your OAuth App. Double check the client_id
and client_secret
to make sure they are correct and being passed correctly to TextMaster.
Redirect URI mismatch
If you provide a redirect_uri
that doesn't match what you've registered with your OAuth App, you'll receive this error message:
To correct this error, provide the same callback URL as registered with your application.
Invalid verification code
If the verification code you pass is incorrect, expired, or doesn't match what you received in the first request for authorization you will receive this error:
To solve this error, start the OAuth authorization process again and get a new code.
Invalid refresh token
If the refresh token you pass is incorrect, expired, or doesn't match what you received in access token request you will receive this error:
To solve this error, start the OAuth access token process again and get a new refresh token.
Timeouts
If TextMaster takes more than 30 seconds to process an API request, TextMaster will terminate the request and you will receive a timeout response. Make sure to use async endpoints when available to overcome this issue.
Last updated