length
null (no offset)
'length' => number_of_records
Can be used in these methods:
search,
browseObjects,
generateSecuredApiKey,
addApiKey,
updateApiKey
search,
browse_objects,
generate_secured_api_key,
add_api_key,
update_api_key
search,
browseObjects,
generateSecuredApiKey,
addApiKey,
updateApiKey
search,
browse_objects,
generate_secured_api_key,
add_api_key,
update_api_key
search,
browse,
generateSecuredApiKey,
addAPIKey,
updateAPIKey
search,
browseObjects,
generateSecuredApiKey,
addApiKey,
updateApiKey
Search,
Browse,
GenerateSecuredApiKey,
AddApiKey,
UpdateApiKey
Search,
browse,
generateSecuredApiKey,
addApiKey,
updateApiKey
Search,
BrowseObjects,
GenerateSecuredAPIKey,
AddAPIKey,
UpdateAPIKey
search,
browse index,
generateSecuredApiKey,
add key,
update key
About this parameter
Set the number of hits to retrieve (used only with offset).
In most cases, page and hitsPerPage is the recommended method for pagination.
This setting is part of an alternative paging approach.
Usage notes
- 1000 is the maximum.
- If
offsetis omitted,lengthis ignored. - If
offsetis specified butlengthomitted, the number of records returned is equal tohitsPerPage. Usingoffsetrequires that you specifylengthas well; otherwise, it defaults to page-based pagination.
Impact on the response:
-
Page-based pagination (page and hitsPerPage):
Copy1 2 3 4 5 6 7
{ ... "page": 1, "nbPages": 20, "hitsPerPage": 10, ... }
-
With offset / length:
Copy1 2 3 4 5 6
{ ... "offset": 5, "length": 10, ... }
Examples
Get n results
1
2
3
$results = $index->search('query', [
'length' => 4
]);