# Rate Limits

To ensure fair use and maintain performance across our platform, we apply rate limits to specific actions such as content syncing, user creation, and content submission. These limits vary depending on your plan (free vs. paid) and can be customized for enterprise customers.

#### Standard Limits

| Action                              | Default Limit  |
| ----------------------------------- | -------------- |
| Content Create/Update               | 300 per minute |
| Content Create/Update Synchronously | 120 per minute |
| User Create/Update                  | 300 per minute |

> **Note:** Limits are subject to change. Enterprise customers can request custom rate limits via support.

#### Headers

All rate-limited responses include headers that provide visibility into your usage:

| Header                  | Description                                          |
| ----------------------- | ---------------------------------------------------- |
| `X-RateLimit-Limit`     | Total allowed requests in the current interval       |
| `X-RateLimit-Remaining` | Number of remaining requests in the current interval |
| `X-RateLimit-Reset`     | Milliseconds until the rate limit resets             |

#### Exceeding Limits

If a rate limit is exceeded, you’ll receive a `429 Too Many Requests` response:

```json
{
  "error": "Too many requests, check headers for limits"
}
```

Use the response headers to determine when you can retry your request.

#### Best Practices

* Implement client-side backoff based on the `X-RateLimit-Reset` header.
* Monitor rate-limiting headers in your integration to prevent service disruption.
* If you're regularly hitting limits, consider upgrading or contacting support for a custom plan.

#### Need Higher Limits?

Enterprise customers may configure custom rate limits per action. Reach out to your account representative to discuss your needs.