Rate Limits

Overview

The Kobble API operates under a reasonable use policy to ensure fair access and system stability for all customers. While we accept all requests, we monitor usage patterns and may implement restrictions if usage exceeds reasonable thresholds.

Reasonable Use Policy

How It Works

Requests Accepted: All API requests are accepted and processed normally

Monitoring: We continuously monitor API usage patterns across all customers

Protection: If usage exceeds reasonable thresholds, we may temporarily restrict access to protect system stability

Notification: Customers will be notified if restrictions are applied

What Constitutes Reasonable Use?

Reasonable use varies based on:

Your typical usage patterns

The type of operations being performed

System capacity and load

Time of day and traffic patterns

We understand that usage can vary, and occasional spikes are normal. However, sustained high-volume traffic or patterns that indicate potential abuse may trigger our protection mechanisms.

Planned Bursts and High-Volume Operations

Notify Us in Advance

If you anticipate a known burst or high-volume operation, please notify us in advance so we can:

Prepare our infrastructure to handle the increased load safely

Ensure optimal performance for your operations

Prevent any potential restrictions during your critical operations

Coordinate capacity to support your needs

Examples of Operations That May Require Notification

Bulk data imports or migrations

Scheduled batch processing jobs

Marketing campaigns or promotions

End-of-period reconciliation runs

Large-scale user onboarding events

Scheduled maintenance windows with retry storms

How to Notify Us

Contact your account manager or support team with:

Expected volume: Number of requests per minute/hour

Duration: How long the burst will last

Time window: When the operation will occur (include timezone)

Endpoints affected: Which API endpoints will be used

Business context: Brief description of the operation

We recommend providing at least 48 hours notice for planned bursts to ensure we can accommodate your needs.

Best Practices

1. Implement Exponential Backoff

When retrying failed requests, use exponential backoff to avoid overwhelming the API:

2. Batch Operations When Possible

Instead of making many individual requests, use batch endpoints when available:

3. Use Idempotency Keys

Always use idempotency keys for POST requests to prevent duplicate operations and reduce unnecessary retries:

See Idempotency Documentation for more details.

4. Monitor Your Usage

Track your API usage patterns to:

Identify unexpected spikes

Plan for capacity needs

Optimize request patterns

Prepare notifications for planned bursts

5. Handle Rate Limit Responses Gracefully

If you receive rate limit responses (HTTP 429), implement appropriate backoff:

Response Codes

Status Code	Meaning	Action
`200 OK`	Request successful	Continue normally
`429 Too Many Requests`	Rate limit exceeded	Implement backoff and retry
`503 Service Unavailable`	Temporary service issue	Retry after delay

Questions or Concerns?

If you have questions about:

Whether your usage patterns are reasonable

Planning for upcoming high-volume operations

Understanding rate limit responses

Optimizing your API usage

Please contact your account manager or our support team. We're here to help ensure your integration runs smoothly.

Overview#

Reasonable Use Policy#

How It Works#

What Constitutes Reasonable Use?#

Planned Bursts and High-Volume Operations#

Notify Us in Advance#

Examples of Operations That May Require Notification#

How to Notify Us#

Best Practices#

1. Implement Exponential Backoff#

2. Batch Operations When Possible#

3. Use Idempotency Keys#

4. Monitor Your Usage#

5. Handle Rate Limit Responses Gracefully#

Response Codes#

Questions or Concerns?#