Spans

Delete spans

Changed on

Permanently deletes spans by their span IDs. This operation is irreversible.

Accepts between 1 and 5000 span IDs per request. Only spans within the searched time window are considered; spans outside that window are not affected.

The optional start_time and end_time fields scope the search to a specific time window. Each bound is independent: omitting start_time defaults to two years ago; omitting end_time defaults to now. You may provide either or both. Providing them when the approximate timestamp of the target spans is known significantly reduces the amount of span data the server must search.

A 200 OK response always includes:

  • completed — true if the operation finished and no retry is needed; false if the operation could not fully complete (retry the full request).
  • deleted_span_ids — span IDs confirmed deleted in this request.
  • not_deleted_span_ids — requested IDs not deleted: either not found within the supported time range, or not reached when completed is false.

The delete operation is idempotent — re-submitting already-deleted IDs is safe.

<Note>This endpoint is in beta, read more here.</Note>

delete/v2/spans

Request

  • Base URL
    https://api.arize.com
  • URL
    https://api.arize.com/v2/spans
  • Auth
    HTTP bearer

Request body

project_idstring required

The project ID containing the spans to delete

span_idsstring[] required

List of span IDs to delete (maximum 5000)

start_timestring date-time

Scope the delete to spans starting at or after this timestamp (inclusive). ISO 8601 format (e.g., 2024-01-01T00:00:00Z). Each bound is independent: omitting start_time defaults to two years ago; omitting end_time defaults to now. You may provide either or both.

end_timestring date-time

Scope the delete to spans starting before this timestamp (exclusive). ISO 8601 format (e.g., 2024-01-02T00:00:00Z). Each bound is independent: omitting start_time defaults to two years ago; omitting end_time defaults to now. You may provide either or both.

Response

Spans deleted. The response body always includes:

  • completed: whether all requested spans were fully processed. This endpoint is idempotent — retries are safe.
  • deleted_span_ids: IDs of spans confirmed deleted.
  • not_deleted_span_ids: IDs of spans not deleted — either not found, or not yet processed when completed is false.
completedboolean required

true when the server fully processed all data for the request — both lists are complete and no retry is needed. false when processing could not fully complete; retry the original request. Note: completed reflects whether all data was processed, not whether all requested spans existed.

deleted_span_idsstring[] required

Span IDs confirmed deleted in this request.

not_deleted_span_idsstring[] required

Requested span IDs that were not deleted. When completed is true, these were not found in the system (never ingested or already deleted). When completed is false, some IDs may not have been reached — retry to resolve them.

Changes

  • 4f94eb2fd1abRevision changes
    • breaking

      removed the success response with the status

    • info

      api operation id spans_delete removed and replaced with delete_spans

    • info

      added the new optional request property

    • info

      added the new optional request property

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the success response with the status