To prevent abuse and undue stress on the system the Data API has a rate limiting feature (sometimes called throttling) that restricts the requests of users.
Lucid recommends that you design your integration to gracefully handle this rate limit error. One way of doing that would be to have your integration sleep for 60 seconds when this error is encountered, and then subsequently retry the request. Alternatively, you might choose to implement exponential backoff, an error handling strategy whereby you periodically retry a failed request with progressively longer wait times between retries until either the request succeeds or the certain number of retry attempts is reached.
The error can be identified by having a 429 Too Many Requests status code.
| Hard Refresh Interval | 30 seconds since last |
| Soft Refresh Interval | 30 seconds since last |
| User API Rate | 750 requests per minute |
| File Size Limit | 3 MB |