Delete an asset timeline entry

Request#

DELETE /api/v1/assets/{record}/timeline/{type}/{entry}

Requires assets:read and assets:timeline:delete. For a todo entry, assets:todos is required as well. See token permissions.

Send Authorization: Bearer YOUR_API_TOKEN and Accept: application/json. Send the request body as JSON with Content-Type: application/json. This write requires Idempotency-Key. Reuse the same key only when retrying the same action.

Path parameters#

record integer Required

The numeric asset ID in your token’s organization.

type string Required

asset_event for an event recorded on this asset, or todo for one of its to-dos. This matches the type in the timeline.

entry integer Required

The entry’s event_id from the timeline, or the to-do id.

Query parameters#

This endpoint does not use query parameters.

Request body#

Example#

Set ASSETCENTER_API_TOKEN as described in the quick start. Replace example record and option IDs with values from your organization. Set IDEMPOTENCY_KEY to a new UUID for this action; keep it for retries. Set VERSION to the version from your latest GET.

curl --request DELETE "https://my.assetcenter.app/api/v1/assets/123/timeline/asset_event/901" \
  --header "Authorization: Bearer $ASSETCENTER_API_TOKEN" \
  --header "Accept: application/json" \
  --header "Idempotency-Key: $IDEMPOTENCY_KEY" \
  --header "Content-Type: application/json" \
  --data '{"version":"VERSION"}'

Response#

200 OK.

{
  "data": {
    "entry_id": 901,
    "entry_deleted": true
  }
}

Behavior and constraints#

Deletes the entry with its comments and attachments; the asset itself is kept. Deletion cannot be undone. Check can_delete from get the entry first: entries the organization’s rules protect from deletion return 403. A stale version returns 409. Deleting a decommission event restores the asset’s earlier status, keeping any storage location; if that would exceed your plan’s asset limit, the request returns 422 with a plan error and nothing is deleted. Retrying with the same key replays the original response after the entry is gone.

Errors#

401 means the token is missing, expired, revoked, or not a customer API token. 403 means a required permission or administrator access is missing. 404 means the record or child record is unavailable in this organization. 422 identifies invalid or unsupported input; inspect the errors object when present. 409 indicates a conflicting state or concurrent change; inspect the message and refresh the record before deciding how to proceed. Reusing an idempotency key with a different method, path, or body also returns 409. 429 means a rate limit was reached. See error handling and rate limits.