Bulk Remove an Organization's Issues

DELETE /api/0/organizations/{organization_id_or_slug}/issues/

Permanently remove the given issues. If IDs are provided, queries and filtering will be ignored. If any IDs are out of scope, the data won't be mutated but the endpoint will still produce a successful response. For example, if no issues were found matching the criteria, a HTTP 204 is returned.

Path Parameters

organization_id_or_slug (string)
REQUIRED

The ID or slug of the organization the resource belongs to.

Query Parameters:

environment (array(string))

The name of environments to filter by.

project (array(integer))

The IDs of projects to filter by. -1 means all available projects. For example, the following are valid parameters:

  • /?project=1234&project=56789
  • /?project=-1
id (array(integer))

The list of issue IDs to be removed. If not provided, it will attempt to remove the first 1000 issues.

query (string)

An optional search query for filtering issues. A default query will apply if no view/query is set. For all results use this parameter with an empty string.

viewId (string)

The ID of the view to use. If no query is present, the view's query and filters will be applied.

sort (string)
choices:
  • date
  • freq
  • inbox
  • new
  • trends
  • user

The sort order of the view. Options include 'Last Seen' (date), 'First Seen' (new), 'Trends' (trends), 'Events' (freq), 'Users' (user), and 'Date Added' (inbox).

limit (integer)

The maximum number of issues to affect. The maximum is 100.

Scopes

<auth_token> requires one of the following scopes:
  • event:admin
Copied
curl https://sentry.io/api/0/organizations/{organization_id_or_slug}/issues/ \
 -H 'Authorization: Bearer <auth_token>' \
 -X DELETE
RESPONSE
Copied
No Content.
Was this helpful?