Bulk delete multiple requests from the space

Deletes multiple requests simultaneously from the specified space. This operation executes asynchronously and
returns an operation ID for tracking deletion progress. Ideal for batch cleanup operations or removing multiple
outdated requests at once. Only users with appropriate management permissions can perform bulk deletions, and
proper audit trails are maintained for all deletion operations.

Key Features:

  • Deletes multiple requests simultaneously for efficient batch operations
  • Executes asynchronously to handle large deletion sets without timeout
  • Returns operation ID for tracking bulk deletion progress and results
  • Validates user permissions for all specified requests before deletion
  • Maintains comprehensive audit trails for compliance and tracking
  • Ensures data consistency across related entities during deletion

Authorization Logic:

  1. User must have a valid JWT token with program management scopes
  2. User must have delete permissions for all specified requests
  3. User must have access to the space containing the requests

Usage Example:

Remove multiple cancelled or outdated content requests from a completed campaign, or clean up test requests created during system configuration to maintain organized program spaces.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
length between 7 and 22

The unique identifier of the space containing the target entity. This determines the scope of entity queries and ensures proper access control. The space must be accessible to the authenticated user with appropriate permissions. It can be the unique identifier (GUID) of the space or the word "default" to indicate the default programs space. Common values include "default" and "rkr83lapKkyCJuLLWqLqzB".

Body Params

Request body containing the request IDs to delete.

ids
array of strings

Array of unique request identifiers to be deleted in the bulk deletion operation. Each ID must be a valid request identifier in base64url or GUID format (e.g., wF53wRD4vky4KTsaRBvGPg) corresponding to existing requests within the specified space. Required field that cannot be empty - must contain at least one request ID. All specified requests must exist in the target space and the authenticated user must have delete permissions for each request. The deletion operation validates all IDs before execution and will fail if any ID is invalid, malformed, or references a non-existent request. Use this array to perform efficient batch cleanup of multiple requests simultaneously, such as removing cancelled requests from completed campaigns or deleting test requests after system configuration. Maximum recommended array size depends on system constraints and timeout limits. Format examples: ['wF53wRD4vky4KTsaRBvGPg', 'xG64xSE5wlz5LUsaRCwHQh', 'yH75yTF6xmz6MUvcTDyIRj']. All deletions execute asynchronously and maintain audit trails for compliance tracking.

ids
Responses

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json