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.Documentation Index
Fetch the complete documentation index at: https://docs.prontohq.com/llms.txt
Use this file to discover all available pages before exploring further.
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
- 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