---
title: "Limitations"
description: "Rate limiting and request limitations in the Fenerum API"
url: https://www.fenerum.com/en-DK/docs/api/guides/limits/
updated_at: "2025-12-22T00:00:00"
---
## Rate Limiting

The Fenerum API uses rate limiting to ensure fair usage and maintain service quality for all users.

### Rate Limits

The default rate limit is **60 requests per minute** per API user.

Rate limits may vary based on your plan:

- **Default**: 60 requests per minute
- **Custom**: Higher limits available on request

### Rate Limit Headers

When you exceed the rate limit, you'll receive a **429 Too Many Requests** response with a `Retry-After` header:

```
<!-- filename: Response -->
HTTP/1.1 429 Too Many Requests
Retry-After: 42
```

| Header                                                  | Description                                             |
| ------------------------------------------------------- | ------------------------------------------------------- |
| `Retry-After`                                           | Number of seconds to wait before making another request |

The response body will include details about the throttling:

```json
<!-- filename: Response -->
{
  "detail": "Request was throttled. Expected available in 42 seconds."
}
```

### Best Practices

#### 1. Respect Retry-After Header

When you receive a 429 response, use the `Retry-After` header value and add a small buffer:

```python
<!-- filename: retry_logic.py -->
import time

def make_request_with_retry(url, max_retries=3):
    for attempt in range(max_retries):
        response = requests.get(url, headers=headers)

        if response.status_code != 429:
            return response

        # Use Retry-After header value + 1 second buffer
        retry_after = int(response.headers.get('Retry-After', 60))
        time.sleep(retry_after + 1)

    return response
```

#### 2. Batch Operations

Where possible, use batch endpoints to reduce the number of requests:

- Create multiple draft invoice lines in a single request
- Use filtering to retrieve only needed data

#### 3. Cache Responses

Cache API responses when data doesn't change frequently:

- Organization settings
- Plan definitions
- Product catalogs

### Need Higher Limits?

Contact our support team if you need higher rate limits for your integration.

---

## Navigation

Up: [Subscription management & financial insights on autopilot](https://www.fenerum.com/en-DK/index.md) › [Documentation](https://www.fenerum.com/en-DK/docs.md) › [API Documentation](https://www.fenerum.com/en-DK/docs/api.md)

Full site index: https://www.fenerum.com/llms.txt