|API Method||Description||PHP Ruby JS Python iOS Android C# Java Go Scala name|
|Custom batch|| |
Perform several indexing operations in one API call.
|Browse an index|| |
Get all index content without any record limit. Can be used for backups.
|Get latest logs|| |
Get the logs of the latest search and indexing operations.
|Configuring timeouts|| |
Override the pre-configured timeouts.
|Set extra header|| |
Sends an extra http header to Algolia, for all subsequent queries
Algolia’s architecture is heavily redundant, to provide optimal reliability. Every application is hosted on at least three different servers. As a developer, however, you don’t need to worry about those details. The API Client handles them for you:
- It leverages our dynamic DNS to perform automatic load balancing between servers.
- Its retry logic switches the targeted server whenever it detects that one of them is down or unreachable. Therefore, a given request will not fail unless all servers are down or unreachable at the same time.
Application-level errors (e.g. invalid query) are still reported without retry.
Requests can fail for two main reasons:
- Network issues: the server could not be reached, or did not answer within the timeout.
- Application error: the server rejected the request.
In the latter case, the error reported by the API client contains:
- an HTTP status code indicating the type of error;
- an error message indicating the cause of the error.
The error message is purely informational and intended for the developer. You should never rely on its content programmatically, as it may change without notice.
Did you find this page helpful?
We're always looking for advice to help improve our documentation!
Please let us know what's working (or what's not!).
We're constantly iterating thanks to the feedback we receive.