This page documents an earlier version of the API client. For the latest version, see Delete records matching a filter.
deleteIndex
-
The filter must be included in your
attributesForFaceting
. For more information, see Define filterable attributes. - This operation counts as 1 operation, even if you delete more than one record.
-
This method is subject to rate-limiting.
If you get errors when using this method, check if you’re over the rate limit and wait before sending further indexing requests.
- If you have more than 100 pending requests, your requests will be throttled.
- If you have more than 1,000 pending requests pending, further requests will be rejected.
browse
method,
and then delete the records using deleteObjects
.
For more information, see Should I use the deleteby method for deleting records matching a query?
Limitations
- The
deleteBy
operation can’t be run in parallel. - This method does not accept empty filters or queries.
When deleting large numbers of records be aware of the rate limitations on these processes and the impact on your analytics data.
Examples
Delete records by filter
Delete records by filter and send extra HTTP headers
Parameters
An object with one or more of the following parameters:
filters
facetFilters
numericFilters
tagFilters
aroundLatLng
andaroundRadius
(these two need to be used together)insideBoundingBox
insidePolygon
A list of request options to send along with the query.
Response
Date at which the indexing job has been created.
Response as JSON
This section shows the JSON response returned by the API. Each API client wraps this response in language-specific objects, so the structure may vary. To view the response, use thegetLogs
method.
Don’t rely on the order of properties—JSON objects don’t preserve key order.
JSON