Delete an asset

Request#

DELETE /api/v1/assets/{record}

Requires assets:delete. See token permissions. Every listed permission is required for this endpoint.

Send Authorization: Bearer YOUR_API_TOKEN and Accept: application/json. Send request bodies as JSON with Content-Type: application/json.

record is the numeric asset ID in your token’s organization.

Request body#

No body fields are required. Omit the request body.

Example#

Set ASSETCENTER_API_TOKEN as described in the quick start. Replace example record and option IDs with values from your organization.

curl --request DELETE "https://my.assetcenter.app/api/v1/assets/123" \
  --header "Authorization: Bearer $ASSETCENTER_API_TOKEN" \
  --header "Accept: application/json"

Response#

204 No Content. The response has no body. Do not try to parse JSON.

Behavior and constraints#

Deletion removes owned timeline entries, to-dos, comments, custom-field values, and files. Historical references on other records retain names where available. File cleanup runs after the deletion commits. Use a lifecycle action instead if you need to preserve this record and its history. Attached trackers are disconnected locally and remote disabling is queued. Deletion has no idempotency replay protection.

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. 409 indicates a conflicting state or concurrent change; inspect the message and refresh the record before deciding how to proceed. 429 means a rate limit was reached. See error handling and rate limits.