Use the Usage API to retrieve historical usage data.
Pick the right metric first
The Usage API exposes search volume as two separate metrics, and they return different numbers for identical traffic:
| Metric | Counts |
|---|---|
total_search_requests |
Network calls to the search endpoint. One multi-query call counts as one, however many sub-queries it carries. |
total_search_operations |
Individual queries executed by the engine. Every sub-query inside a multi-query call counts separately. |
If you're reconciling against your invoice, choose deliberately. On plans sold since March 2023, including Grow, you are billed on total_search_requests. Some legacy plans bill on operations instead.
The gap between the two metrics is the number of queries bundled per request, which on a typical search-as-you-type implementation is routinely three to five times. Pulling total_search_operations when you meant requests will overstate your billable usage by that factor.
To confirm which unit applies to your plan, see How Algolia counts search requests, operations, and records.
Retention and granularity
Usage data is retained for up to 3.5 years. Metric values are returned per day, so you'll need to aggregate them yourself to produce monthly or yearly totals.
When aggregating, sum across whole billing periods rather than calendar months if your billing cycle doesn't start on the 1st, or your totals won't line up with your invoices.
Other metrics available
The same API also exposes records, total_indexing_operations, total_records_operations, and queries_above_last_ms_processing_time, among others. See the Usage API reference for the full list.