Batch Request
A batch request combines multiple API calls into a single request. It reduces network overhead and helps stay within rate limits.
Understanding the Concept
Imagine you need prices for 50 assets. You could make 50 separate requests (slow, rate-limit-hungry) or one batch request (fast, efficient). The math is obvious.
Batch requests reduce latency because you eliminate 49 round trips. They reduce rate limit consumption because one request counts as one, even if it returns 50 results. They simplify your code because you handle one response instead of 50.
Not all APIs support batching the same way. Some use comma-separated parameters. Others accept arrays in request bodies. Check the docs.
Real-World Example
Instead of: GET /ticker/bitcoin, GET /ticker/ethereum, GET /ticker/solana (3 requests), use: GET /ticker?symbols=bitcoin,ethereum,solana (1 request). Same data, 1/3 the overhead.
How PRISM Handles This
PRISM supports batch requests across most endpoints. Pass multiple symbols as comma-separated values or JSON arrays. Our /batch endpoint lets you combine different request types in one call. Batch up to 100 items per request.
View API Docs