These are some commonly known problems that you may run into and what they might mean.
Unauthorized error
Sometimes, requests might fail with the following response
{
"error": "Unauthorized"
}
If you have previously been interacting with an endpoint and suddenly you get this error, it most likely indicates that your session token is no longer valid and you need to get a new one.
When this happens, simply make a new request to /api/authenticate, providing your API key, and replace the token in your requests for the new session token.
If it's the first time you try an endpoint and you get this error. And if you know that your session token is valid, because it has been generated recently, it must mean that your API key does not have the right permission to request the endpoint. If you believe you should have permission to do so with your API key, please contact support.
Missing data
If you request an endpoint, such as the list of users, booths or facilities, and you don't see resources that you believe you should see, there are two main possible reasons:
- Pagination is enabled and the missing resources didn't fit in the page. In which case, you can request the next page of results by including the
pageparameter in your request, or you can request larger pages, by including thelimitparameter in your request. - You may not have access to the resources that are missing. API keys are scoped to your account, so you should only be able to view resources that belong to your account. If you think you should have access to a certain resource, but are not seeing it, please contact support.
Unexpected error response
Sometimes you might run into a couple of error codes that are not as usual:
429: too many requests422: API limit reached
If you run into any of these error codes, it most likely means that you hit one of the rate limits of the API. For more information on those, read the Rate Limiting section of this documentation.