What counts as an indexing operation
-
Record operations - each addition, update, or deletion of a record counts as one operation. This applies even when nothing actually changes, for example when the targeted
objectIDdoesn't exist.- In a batch, each record counts separately. That includes deleteObjects, even for an
objectIDthat doesn't exist. - deleteBy is the exception: it can delete many records but counts as one operation.
- In a batch, each record counts separately. That includes deleteObjects, even for an
- Rule operations - each addition, update, or deletion counts as one operation.
- Synonym operations - each addition, update, or deletion counts as one operation.
- ACL operations - each addition, update, or deletion of an API key or its ACL counts as one operation.
- Index operations - every setSettings call counts as one operation, however many settings you change at once. Moving, deleting, clearing, or copying an index each count as one operation.
Limits on plans released July 2020 or later
Indexing operations and getObjects requests are not counted towards your usage on these plans.
There is still a limit, to stop extreme operation volumes affecting cluster performance: a contractual ceiling of 10,000 indexing operations for every 1,000 search requests and records used per month. Exceeding it produces an error rather than a charge.
Limits on older plans
Some legacy plans do count indexing operations against an allotted operation quota. Most have a monthly quota that varies by plan, and operations beyond it are subject to overage charges.
You can see your plan and its monthly allowance in the Billing overview section of your dashboard. If no limit is shown, your plan may have a customised quota stated in your contract — check with your account team or open a Support ticket.
Where to see your numbers
Indexing activity appears in your dashboard under API Monitoring > Usage. See Track usage for a walkthrough, or pull the figures programmatically with the Usage API.