# ObservePoint API Rate Limiting The ObservePoint API implements industry standard rate limiting practices. If your code generates too many API requests in a period of time, the API will respond with a `429` error. API rate limits are enforced per API key. ### What should I do if my API requests get rate limited? Dealing with rate limiting is straight forward. If your code receives a `429` response, your code should wait and retry later. Usually a few seconds will suffice. Sometimes your code will need to retry for up to 5 minutes. Your code cannot cause harm by continuing to retry when it receives a `429` response. It's a best practice to design your code to handle `429` responses from the beginning. Don't wait until you encounter your first `429` response to write the code. ## What is the API rate limit? The rate limit varies between API endpoints, but as a general rule, the API will allow between 100 and 600 requests per minute, with some endpoints allowing 1,000 requests per minute. ObservePoint occasionally changes rate limits to ensure the API can operate reliably. ## Will I be charged if I hit the API rate limit? You will not be billed if your code gets rate limited.