> ## Documentation Index > Fetch the complete documentation index at: https://docs.didit.me/llms.txt > Use this file to discover all available pages before exploring further. # Delete Monitoring Event > Permanently delete one monitoring event with its rule runs, notes and tags. It disappears from every read and the deletion is irreversible. Delete Monitoring Event API Prompt Copy prompt to clipboard 
  \`Permanently delete one monitoring event from my Didit application.

  Endpoint:
  DELETE [https://verification.didit.me/v3/events/\{event\_uuid}/delete/](https://verification.didit.me/v3/events/\{event_uuid}/delete/)

  Authentication:
  Use the x-api-key header with my Didit API key. A scoped key needs transactions: write.

  Goal:

  * Delete a single event, for example one sent by mistake. To erase everything about a person or a company, delete the user or the company instead, which also deletes their events.

  Behavior:

  * event\_uuid is the Didit id of the event (from the create, batch, list or timeline response), not my own event\_id.
  * The event is deleted together with its rule runs, notes and tag links.
  * After a 204 the event no longer appears in any read: GET /v3/events/{event_uuid}/ returns 404 and it is gone from the list and the subject timeline.
  * Deletion is irreversible. A second call returns 404.
  * Not affected: the user or company the event resolved to, cases a rule opened, and list entries a rule added. They are separate records with their own lifecycle.
  * The event\_id becomes free: a later POST /v3/events/ with it stores a new event.

  Example call:
  curl -X DELETE "[https://verification.didit.me/v3/events/11111111-2222-3333-4444-555555555555/delete/](https://verification.didit.me/v3/events/11111111-2222-3333-4444-555555555555/delete/)" \
  -H "x-api-key: YOUR\_API\_KEY"

  What to read from the response:

  * 204 No Content means the event was deleted. There is no body.

  Failure modes:

  * 401 - the API key has expired.
  * 403 - missing or invalid API key, or a scoped key without transactions: write.
  * 404 - no event with this event\_uuid in the application (already deleted, never stored, or another application's).

  Side effects: permanently deletes the event. This cannot be undone.

  For the full integration shape, see /integration/integration-prompt.\`
Paste into > [!WARNING] > > Deleting an event is irreversible. To erase everything about a person or a company, [delete the user](/management-api/users/delete.md) or [delete the company](/management-api/businesses/delete.md) instead of deleting their events one by one: that also deletes their events. ## OpenAPI ````yaml DELETE /v3/events/{event_uuid}/delete/ openapi: 3.0.0 info: version: 3.0.0 title: Didit Verification API description: Identity verification API. Authenticate with x-api-key header. servers: - url: https://verification.didit.me security: [] tags: [] paths: /v3/events/{event_uuid}/delete/: delete: tags: - Monitoring Events summary: Delete monitoring event description: >- Permanently delete one monitoring event together with its rule runs, notes and tag links, for example an event sent by mistake. After the `204` the event is gone from every read (retrieve returns `404`, and it no longer appears in the list or the subject timeline), the deletion is irreversible, and its `event_id` is free to be used for a new event. Not affected: the user or company the event resolved to, cases a rule opened, list entries a rule added, and the scores and statuses already applied to other events. To erase everything about a person or a company, delete the user or the company instead, which also deletes their events. A scoped API key needs `transactions: write`. operationId: delete_monitoring_event parameters: - name: event_uuid in: path required: true description: >- Didit identifier of the event (`event_uuid` from the create, batch, list or timeline response), not your own `event_id`. schema: type: string format: uuid example: 11111111-2222-3333-4444-555555555555 responses: '204': description: The event was deleted. No body. '401': description: >- The scoped API key has expired. Only an expired key gets `401`; a missing or invalid key gets `403`. content: application/json: examples: Expired key: value: detail: This API key has expired. '403': description: >- Missing or invalid `x-api-key` (this endpoint answers `403`, never `401`, for a missing or invalid key), a scoped key without `transactions: write`, a key limited to some workflows or to approved sessions (such a key never reaches transaction monitoring data), or a request from outside the key's IP allowlist. content: application/json: examples: Missing or invalid API key: value: detail: You do not have permission to perform this action. Scoped key without access: value: detail: This API key has no write access to transactions. Key limited to workflows or approved sessions: value: detail: >- This API key only reaches sessions inside its workflow or status limits, so it can't use this endpoint. IP not allowed: value: detail: This API key can't be used from this IP address. '404': description: >- No event with this `event_uuid` exists in the application: it was never stored, it was deleted, or it belongs to another application. A path segment that is not a UUID does not match the route and also returns `404`. content: application/json: examples: Not found: value: detail: No MonitoringEvent matches the given query. '429': description: >- Rate limit exceeded: write requests (`POST`, `PATCH`, `DELETE`) share a budget of 300 requests per minute per API key. Wait `Retry-After` seconds, then retry. headers: Retry-After: description: Seconds to wait before retrying. schema: type: integer minimum: 1 example: 30 content: application/json: examples: Throttled: value: detail: >- Write request rate limit exceeded. You can make up to 300 requests per minute. security: - ApiKeyAuth: [] x-codeSamples: - lang: curl label: curl source: >- curl -X DELETE 'https://verification.didit.me/v3/events/11111111-2222-3333-4444-555555555555/delete/' \ -H 'x-api-key: YOUR_API_KEY' - lang: python label: Python source: |- import os import requests event_uuid = '11111111-2222-3333-4444-555555555555' resp = requests.delete( f'https://verification.didit.me/v3/events/{event_uuid}/delete/', headers={'x-api-key': os.environ['DIDIT_API_KEY']}, timeout=10, ) resp.raise_for_status() # 204 No Content print('deleted', event_uuid) - lang: javascript label: JavaScript source: >- const eventUuid = '11111111-2222-3333-4444-555555555555'; const resp = await fetch(`https://verification.didit.me/v3/events/${eventUuid}/delete/`, { method: 'DELETE', headers: { 'x-api-key': process.env.DIDIT_API_KEY }, }); if (resp.status !== 204) throw new Error(`Delete failed: ${resp.status}`); console.log('deleted', eventUuid); components: securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: >- Your application's API key, from Developers -> API keys in the Business Console. The primary key has full access. A named key can be scoped: none, read or write per resource, limited to some workflows or to approved sessions, to a list of IP addresses, and to an expiry date. 401 means the key is missing, wrong, revoked or expired; 403 means the key has no access to this resource or action, or the request came from an address outside its IP list; 404 on a session route means the session is outside the key's workflows or statuses. A key without media access receives image, video and PDF URLs as null, and a key without sessions write receives session links and tokens as null. See https://docs.didit.me/console/api-keys. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.