Delete by query

delete/admin/data
Internal-Use Only

Deletes all of the indexed objects and relationships matching the given query. If no request body is provided, then all of the indexed objects and relationships will be deleted. This operation cannot be undone without first making a backup of the indexed data directly from the underlying search engine.

Request Samples

1

Response Samples

1No example avaliable

Query Parameters

NameTypeRequiredDescription
excludeCategoryAliases
boolean
false

Whether type category aliases should be excluded from the search. In particular, this should be set to true when the intention is to delete system relationships without deleting custom relationships as they both share the same type category alias.

Default:
false
preserveNewestIndexName
boolean
false

Whether to preserve and reuse the name of the newest index for each type when creating the next searchable index. Creating new unsearchable indexes, or deleting indexes without this option, will cause the new indexes to have new unique names. Preserving the newest index name is useful when maintaining a read-only standby deployment for Disaster Avoidance as it allows the data to be re-indexed without changing the index name. For example, when applying a breaking configuration change from the active deployment.

Default:
false
waitForRefresh
boolean
false

Whether to wait for any index-related operations to be applied prior to the response being returned.

Default:
false

Request Body

The request to perform an action on data specified by a query.

NameTypeRequiredDescription
version
integer
false

The representation version (2).

types
array [string]
false

The optional list of type names for the object and relationship types to be searched. If missing, all types will be searched.

query
Query or anyOf
QueryTypeAndQueryTypeCompoundQueryTypeObjectQueryTypeOrQueryTypeText
false

The different query types that can be used to search for objects. See specific query definitions for more details.

Responses

StatusMeaningDescription
204No ContentThe request succeeded.
400Bad RequestThe request is malformed or contains invalid parameter values.Schema