Counting indexing operations
We count the following indexing operations:
Record operations: each addition, update, or deletion on a record counts as one operation. This happens even when nothing changes (for example, if the targeted
- 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, even if you change several settings at once.
- Moving, deleting, clearing, or copying an index counts as one operation.
Indexing operations limitations
For plans released July 2020 and newer
We don’t count indexing operations or getObjects requests towards your usage for users on our Free, Standard, and Premium PAYG (Pay-As-You-Go) plans and our latest plans. However, to prevent extreme numbers of operations impacting your cluster, we implemented a protective limit of 10,000 indexing operations per unit per month. When exceeding this limit, you may get an error message informing you that you reached the indexing limit, so you can reduce the number of indexing operations accordingly.
For older plans
Legacy plans have monthly operations limitations dependent on the plan. You can see an application’s plan and amount of allotted monthly operations from the 'billing overview' section of your Algolia dashboard.
Please keep in mind that some legacy plans count search operations towards the allotted limit, and operations beyond the limit are subject to overage charges.
If you don’t see a limit here, your plan may have a customized quota stated in your contract. If you are unsure of your operations limitations, please contact your account team or open a Support ticket.