API Documentation home page
Search...
⌘K
Contact Support
Pronto Dashboard
Pronto Dashboard
Search...
Navigation
API Essentials
Bulk vs Single operations
Documentation
API Reference
Documentation
Go to Dashboard
Blog
Getting started
Overview
API Essentials
Authentification
Credits
Rate Limiting
Concurrency
Bulk vs Single operations
Async Results
On this page
Single Request Endpoints
Bulk Request Endpoints
When to Use Each
Best Practices
API Essentials
Bulk vs Single operations
Understanding bulk and single request endpoints
When working with the Pronto API, you’ll encounter two types of endpoints: bulk and single request endpoints. Understanding the differences and when to use each type is crucial for optimizing your API usage.
Single Request Endpoints
Single request endpoints are designed for processing one item at a time. These endpoints:
Return results immediately
Are ideal for real-time operations
Have lower latency
Are perfect for interactive applications
Bulk Request Endpoints
Bulk endpoints allow you to process multiple items in a single API call. These endpoints:
Are more efficient for large datasets
Usually operate asynchronously
Provide better throughput
Help you stay within rate limits
Are cost-effective for batch processing
When to Use Each
Use single request endpoints when:
You need immediate results
Processing one-off requests
Building interactive features
Working with small data volumes
Use bulk endpoints when:
Processing large datasets
Running batch operations
Optimizing for cost and efficiency
Working with lists of items
Best Practices
Batch Size
: When using bulk endpoints, aim for batch sizes between 100-1000 items for optimal performance
Error Handling
: Implement proper error handling for both types of endpoints
Rate Limits
: Consider rate limits when choosing between bulk and single endpoints
Concurrency
Async Results
Assistant
Responses are generated using AI and may contain mistakes.