Overview
The Vepler API uses offset-based pagination for list and query endpoints. Requests acceptlimit and offset parameters, and responses indicate whether more data is available.
Request Parameters
Response Format
Paginated responses include metadata alongside the results:Basic Usage
First Page
Subsequent Pages
Complete Iteration Example
Query Endpoint Pagination
For POST query endpoints, pagination parameters are in the request body:Best Practices
Use Appropriate Page Sizes
Use Appropriate Page Sizes
- Use larger page sizes (50-100) for bulk operations
- Use smaller page sizes (10-25) for user-facing displays
- Check each endpoint’s documentation for maximum allowed values
Add Delays Between Pages
Add Delays Between Pages
When iterating through many pages, add a small delay to avoid hitting usage limits:
Use Field Selection
Use Field Selection
Reduce response size by requesting only the fields you need:
Next Steps
Error Handling
Handle errors effectively
Usage & Limits
Understand usage metering