Managing Items and Permissions
- Adding or Updating a Single Basic Item in a Public Push Source
- Adding or Updating a Single Item in a Push Source
- Deleting an Item and Optionally its Children
- Deleting Old Items in a Push Source
- Managing Batches of Items in a Push Source
- Pushing Item Data
- Understanding Push Source Item Metadata
- Simple Permission Model Definition Examples
- Complex Permission Model Definition Example
- Understanding the parentId Property
- Item Models
Deleting an Item and Optionally, its Children in a Push Source
Use the Delete an item and optionally its children operation to remove an item from a specific Push source.
You should never use this operation repetitively to delete many items in a Push source (i.e., to perform a large scale content update). When this is what you need to do, depending on what you want to achieve, you should either use:
DELETE https://api.cloud.coveo.com/push/v1/organizations/<MyOrganizationId>/sources/<MySourceId>/documents?deleteChildren=<true|false>&documentId=<MyItemURI> HTTP/1.1 Authorization: Bearer <MyAccessToken>
In the request path:
<MyOrganizationId>with the actual ID of the target Coveo organization (see Retrieving the ID of a Coveo Cloud V2 Organization).
In the query string:
trueif you want to recursively delete all items matching the
/; set it to
This means that the following request:
DELETE https://api.cloud.coveo.com/push/v1/organizations/mycoveocloudv2organizationg8tp8wu3/sources/mycoveocloudv2organizationg8tp8wu3-rp5rxzbdz753uhndklv2ztkfgy/documents?deleteChildren=true&documentId=file%3A%2F%2Ffolder HTTP/1.1 Authorization: Bearer **********-****-****-****-************
will recursively delete all items whose
file://folder/*from the target Push source (e.g.,
<MyItemURI>with the URL-encoded URI of the item to delete in the target Push source (e.g.,
Authorization HTTP header:
<MyAccessToken>with an access token that grants the Organization - View and Sources - View/Edit privileges in the target Coveo organization (see Creating an API key, Getting the Privileges of an Access Token, and Getting Your Coveo V2 Platform Access Token).
A successful response (
202 Accepted) indicates that the delete operation was successfully forwarded to the service and is now enqueued to be processed in the Coveo Cloud indexing pipeline.
This doesn’t imply that the item was successfully deleted in the target Push source (see Understanding the Push API Processing Delay).
Update the status of your Push source
If you set your Push source to an active status before, you should consider setting it back to the
IDLE status once this operation has successfully returned, assuming you have no more operations to perform as part of this content update (see Updating the Status of a Push Source).
Deleting an item and its children
DELETE https://api.cloud.coveo.com/push/v1/organizations/mycoveocloudv2organizationg8tp8wu3/sources/mycoveocloudv2organizationg8tp8wu3-rp5rxzbdz753uhndklv2ztkfgy/documents?deleteChildren=true&documentId=file%3A%2F%2Ffolder%2F HTTP/1.1 Authorization: Bearer **********-****-****-****-************
Successful response - 202 Accepted