Skip to main content

Overview

The Vepler API meters usage on a per-request basis. Your API usage is tracked and billed according to your subscription plan. If you exceed your plan’s limits, the API will return a 429 Too Many Requests response.

Handling 429 Responses

When you exceed your usage limits, the API returns a 429 status code:

Retry with Exponential Backoff

Implement exponential backoff when you receive a 429 response:

Best Practices

1. Use Batch Endpoints

Where available, use batch endpoints to fetch multiple records in a single request:

2. Cache Responses

Cache frequently accessed data to reduce API calls:

3. Use Request Queuing

Queue requests to control throughput:

4. Select Only the Fields You Need

Use the attributes parameter to request only the fields you need, reducing response size and improving performance:

Increasing Your Limits

If you need higher usage limits:
  1. Upgrade your plan at app.vepler.com
  2. Contact sales at sales@vepler.com for enterprise requirements

Next Steps

Error Handling

Handle errors effectively

API Reference

Explore all endpoints