Atlato Developer
DocsUse CasesCommunitySupport
DocsUse CasesCommunitySupport
Facebook
Linkedin
Instagram
  1. API Request
  • Overview
    • Developer Platform
  • Getting Started
    • Register Account
    • Manage Apps
    • Manage a Company
    • App Access
    • Store App Access
    • Mode
  • App Store
    • Authentication
    • Access Rights
    • Event Log
    • Company Settings
    • Manage Account
  • Device Integration
    • Design
    • Installation
    • Device List
  • Device API
    • Protocols
    • New Integration
    • Data Output
    • Device Input Names
  • Deployment
    • Custom Client App
  • API Request
    • REST API
    • Request Structure
    • Metadata
    • Pagination
    • Errors
    • Troubleshooting
  • Support
    • Developer Request Types
  • Guides
    • Best practices
    • Timezones
    • Libraries
    • Key Concepts
    • Terms of Use
    • Rate limits
  • Feedback Center
    • Feedback
    • Community
    • FAQ
  • Api Integration
    • Use token in your app
    • Event Logging API
    • Meta Data API
    • Lastest Device Data API
    • Past Device Data API
    • Devices API
    • Country City Currency API
  • App Integration APIs
    • Meta Data
    • Meta Data API
    • Lastest Device Data API
    • Past Device Data API
    • Event Logging API
    • Devices API
    • Country City Currency API
  • Developer Platform
    • Access
    • User
    • Device
    • Manage Account
    • Company
  1. API Request

Troubleshooting

Access denied errors#

If you recieve a 403 Forbidden response, that means the request does not have enough permissions to call that API request. check the role access rights assigned to that user who initiatd the request. Also try to refresh the access token by login out and login in again.

Rate limit errors#

If you recieve a 429 Too Many Requests response, that means you have exceeded the number of api requests per day (300 requests). Continuing to make requests while you are rate limited may result in the banning of your account. Wait for the limit to rest at 12 midnight everyday and retry.

Not found error#

If you recieve a 404 not found response, that means you should check for typos in your URL. For example, adding /deviec instead of /device to the endpoint will result in a 404 Not Found.
It can also due to the resource you are trying to access has been deleted or moved. You can refer to the reference api documentation for the endpoint to confirm that you have the correct URL.

Timeouts#

If it takes more than 20 seconds to process an API request, platform will terminate the request and you will receive a timeout response and a 500 internal server error message.
Atlato reserves the right to change the timeout window to protect the speed and reliability of the API.
You can try to simplify your request or try your request later. For example, if you are requesting 100 days of data, you can try requesting data by 10 day period.

Validation Failed#

If you recieve 400 BAD_REQUEST response, it could mean the following
A parameter that was required was not specified. Review the documentation for the endpoint to see what parameters are required.
The formatting of a parameter is invalid. Review the endpoint documentation for more specific information
The parameters that were provided were invalid.
The data types of the provided parameters do not match the expected types.
The size of the request body exceeds the permissible limits.
Modified at 2024-07-19 08:36:38
Previous
Errors
Next
Support
Built with