Helper methods
Helper methods extend or combine API operations to make using the Search API easier.
Browse for records
Required ACL: browse
Retrieves all records from an index.
This helper method is based on the Browse for records API operation.
It iterates over the paginated API response and aggregates all records.
1
2
3
4
$client->browseObjects(
string $indexName,
array $requestOptions,
)
Parameters
$index_name
|
type: string
Required
Index name from which to get all records. |
$requestOptions
|
type: array
default: []
Extra parameters, such as headers or query parameters. For more information, see Request options. |
Browse for rules
Required ACL: settings
Retrieves all rules from an index.
This helper method is based on the Search for rules API operation.
It iterates over the paginated API response and aggregates all rules.
1
2
3
4
$client->browse_rules(
string $indexName,
array $requestOptions,
)
Parameters
$indexName
|
type: string
Required
Index name from which to get all rules. |
$requestOptions
|
type: array
default: []
Extra parameters, such as headers or query parameters. For more information, see Request options. |
Browse for synonyms
Required ACL: settings
Retrieves all synonyms from an index.
This helper method is based on the Search for synonyms API operation.
It iterates over the paginated API response and aggregates all synonyms.
1
2
3
4
$client->browseSynonyms(
string $indexName,
array $requestOptions,
)
Parameters
$indexName
|
type: string
Required
Index name from which to get all synonyms. |
$requestOptions
|
type: array
default: []
Extra parameters, such as headers or query parameters. For more information, see Request options. |
Delete records
Required ACL: deleteObject
Deletes records from an index using their object IDs.
This helper methods is based on the Batch operations on one index API operation.
It constructs the batch write request with the deleteObject
action
and automatically sends requests in batches of 1,000 records.
1
2
3
4
5
$client->deleteObjects(
string $indexName,
array $objectIds,
array $requestOptions,
)
Parameters
$indexName
|
type: string
Required
Index name from which to delete records. |
$objectIDs
|
type: array
items: string
Required
Object IDs to delete. |
$requestOptions
|
type: array
default: []
Extra parameters, such as headers or query parameters. For more information, see Request options. |
Create secured API keys
Creates a secured API key without any calls to Algolia’s servers.
This helper method takes a parent API key and adds restrictions to it, which can’t be changed at query time.
Secured API keys are forms of hash-based message authentication codes (HMAC).
This helper performs these steps to create a secured API key:
-
Compute a SHA-256 HMAC with the parent API key as secret, and a URL-encoded list of query parameters as message. These query parameters will be applied with every use of the API key and can’t be changed by users.
-
Concatenate the SHA-256 HMAC with the list of query parameters to a single string.
-
Encode the whole string in
base64
.
1
2
3
4
$client->generateSecuredApiKey(
string $parentApiKey,
array $restrictions,
)
Parameters
$parentApiKey
|
type: string
Required
The API key to be used as secret for the secured API key. The secured API key inherits all restrictions from this API key. You can’t use an Admin API key. |
restrictions
|
type: array
default: []
Restrictions to apply to the secured API key.
You must add at least one restriction.
If you make requests with a secured API key with the same restrictions as the |
restrictions ➔ restrictions
Restrictions you can add to secured API keys.
searchParams
|
type: array
Search parameters that will always be applied with this API key. For more information, see Search. |
filters
|
type: string
Filters that will always be applied with this API key. |
validUntil
|
type: int
Timestamp when the API key expires, in seconds since the Unix epoch. |
restrictIndices
|
type: array
items: string
Index names that this API key should be allowed to access.
You can use the wildcard character |
restrictSources
|
type: string
IP network range that is allowed to use this API key. |
userToken
|
type: string
Pseudonymous user identifier to restrict usage of this API key to specific users. By default, rate limits are set based on IP addresses. This can be an issue if many users search from the same IP address. To avoid this, add a user token to each generated API key. |
Get secured API key remaining validity
Retrieves the time in seconds until the secured API key expires.
This helper method returns the amount of seconds left until the secured API key expires,
as defined by its validUntil
property.
If the key already expired, this method returns a negative number, indicating the number of seconds since the key expired.
1
2
3
$client->getSecuredApiKeyRemainingValidity(
string $securedApiKey
)
Parameters
$securedApiKey
|
type: string
Required
Secured API key for which to retrieve the time of validity. |
Update attributes of records
Required ACL: addObject
Adds or updates attributes of records
This helper methods is based on the Batch operations on one index API operation.
It constructs the batch write request with the partialUpdateObject
or partialUpdateObjectNoCreate
action
(depending on the createIfNotExists
option)
and automatically sends requests in batches of 1,000 records.
1
2
3
4
5
6
$client->partialUpdateObjects(
string $indexName,
array $objects,
bool $createIfNotExists,
array $requestOptions,
)
Parameters
$indexName
|
type: string
Required
Index name where to update records. |
$objects
|
type: array
items: array
Required
Records to update. |
$createIfNotExists
|
type: bool
Required
Whether to create new records if they don’t exist. |
$requestOptions
|
type: array
default: []
Extra parameters, such as headers or query parameters. For more information, see Request options. |
Replace all records
Required ACL: addObject
Replaces all records in an index with new ones.
This helper lets you replace all records in an index without interrupting the ability to search.
It’s based on the Batch indexing operations on one index and Copy or move an index API operations and performs these actions:
- Copy settings, synonyms, and rules to a temporary index.
- Add the records from the
objects
parameter to the temporary index. - Move the temporary index to the original index to replace it.
If you use an API key with indexes
restrictions, you need to allow access to the index INDEX_NAME_tmp_*
(replace INDEX_NAME
with the name of your original index).
1
2
3
4
5
6
$client->replaceAllObjects(
string $indexName,
array $objects,
int $batchSize,
array $requestOptions,
)
Parameters
$indexName
|
type: string
Required
Index name where to replace all records. |
$objects
|
type: array
items: array
Required
Records that replace the existing records in your index. |
$batchSize
|
type: int
default: 1,000
Batch size for the indexing operation. |
$requestOptions
|
type: array
default: []
Extra parameters, such as headers or query parameters. For more information, see Request options. |
Save records
Required ACL: addObject
Adds records to an index.
This helper methods is based on the Batch operations on one index API operation.
It constructs the batch write request with the addObject
action
and automatically sends requests in batches of 1,000 records.
1
2
3
4
$client->saveObjects(
string $indexName,
array $objects,
)
Parameters
$indexName
|
type: string
Required
Index name to which to add records. |
$objects
|
type: array
items: array
Required
Records to add. |
Wait for API keys
Waits for an API key operation to be finished.
When you add, update, or delete API keys, it might take a while before the change is applied.
1
2
3
4
5
6
7
8
$client->waitForApiKey(
string $operation,
string $key,
?array $apiKey,
?int $maxRetries,
?int $timeout,
array $request_options,
)
Parameters
$key
|
type: string
Required
The API key that was added, update, or deleted. For example, you can get this value from the API response when creating or updating. |
$operation
|
type: string
Required
The type of operation to wait for:
|
$apiKey
|
type: array
default: null
When waiting for an API key to be updated,
|
$maxRetries
|
type: int
default: 50
Maximum number of times the task status should be checked. |
$timeout
|
type: int
default: 5000
Time in milliseconds before checking the status again. |
$requestOptions
|
type: array
default: []
Extra parameters, such as headers or query parameters. For more information, see Request options. |
Examples
Wait until an API key is added:
1
2
3
4
5
6
7
8
use Algolia\AlgoliaSearch\Api\SearchClient;
$client = SearchClient::create('ALGOLIA_APPLICATION_ID', 'ALGOLIA_API_KEY');
$response = $client->waitForApiKey(
'api-key-add-operation-test-php',
'add',
);
Wait until an API key is updated:
1
2
3
4
5
6
7
8
use Algolia\AlgoliaSearch\Api\SearchClient;
$client = SearchClient::create('ALGOLIA_APPLICATION_ID', 'ALGOLIA_API_KEY');
$response = $client->waitForApiKey(
'api-key-add-operation-test-php',
'add',
);
Wait until an API key is deleted:
1
2
3
4
5
6
7
8
use Algolia\AlgoliaSearch\Api\SearchClient;
$client = SearchClient::create('ALGOLIA_APPLICATION_ID', 'ALGOLIA_API_KEY');
$response = $client->waitForApiKey(
'api-key-add-operation-test-php',
'add',
);
Wait for application-level tasks
Waits for an application-level task to complete.
While indexing operations are index-level tasks,
some tasks, such as working with dictionaries,
are application-level tasks.
They’re asynchronous: when you make a request, Algolia adds the task to a queue
and runs it depending on the server load.
The response includes a taskID
property that you can use to wait until the task is complete.
This helper method polls the Check application task status
API operation and stops if the task’s status is published
.
1
2
3
4
5
6
$client->waitForAppTask(
string $taskId,
?int $maxRetries,
?int $timeout,
array $requestOptions,
)
Parameters
$taskId
|
type: string
Required
Task ID for which to wait. |
$maxRetries
|
type: Integer
default: 50
Maximum number of times the task status should be checked. |
$timeout
|
type: int
default: 5000
Time in milliseconds before checking the status again. |
$requestOptions
|
type: array
default: []
Extra parameters, such as headers or query parameters. For more information, see Request options. |
Examples
1
2
3
4
5
6
7
use Algolia\AlgoliaSearch\Api\SearchClient;
$client = SearchClient::create('ALGOLIA_APPLICATION_ID', 'ALGOLIA_API_KEY');
$response = $client->waitForAppTask(
123,
);
Wait for index operations
Waits for an indexing task to complete.
Indexing operations are asynchronous.
When you make a request for an indexing operation, such as, adding or updating records,
Algolia adds a task to a queue and returns a taskID
property with the response.
The task itself runs separately, depending on the server load.
This helper method polls the Check task status
API operation and stops if the task’s status is published
.
1
2
3
4
5
6
7
$client->waitForTask(
string $indexName,
string $taskId,
?int $maxRetries,
?int $timeout,
array $requestOptions,
)
Parameters
$indexName
|
type: string
Required
Index name for which to check the task. |
$taskId
|
type: string
Required
Task ID for which to wait. |
$maxRetries
|
type: Integer
default: 50
Maximum number of times the task status should be checked. |
$timeout
|
type: int
default: 5000
Time in milliseconds before checking the status again. |
$requestOptions
|
type: array
default: []
Extra parameters, such as headers or query parameters. For more information, see Request options. |
Examples
1
2
3
4
5
6
7
8
use Algolia\AlgoliaSearch\Api\SearchClient;
$client = SearchClient::create('ALGOLIA_APPLICATION_ID', 'ALGOLIA_API_KEY');
$response = $client->waitForTask(
'ALGOLIA_INDEX_NAME',
123,
);