/api/v1/asset-events/{event}
Delete an asset event definition
Delete an asset event definition in the organization attached to your public API key.
Last updated
Request
DELETE /api/v1/asset-events/{event}
Requires asset-events:delete and an active token creator who remains an administrator of the token’s organization. Event setup and permissions.
Send Authorization: Bearer YOUR_API_TOKEN and Accept: application/json.
Path parameters
-
eventinteger Required - Definition ID from list definitions. Use the returned replacement ID after customizing a shared default.
Query parameters
This endpoint does not use query parameters.
Retry protection
Requires Idempotency-Key: 8–128 letters, numbers, dots, underscores, colons, or hyphens. Reuse the same method, path, body, and key for retries. Successful responses are remembered for 24 hours per token. Conflicting key reuse returns 409. Idempotency and retries.
Example
Replace the example ID with an ID from your organization. Set ASSETCENTER_API_TOKEN as described in the quick start.
curl --request DELETE "https://my.assetcenter.app/api/v1/asset-events/42" \
--header "Authorization: Bearer $ASSETCENTER_API_TOKEN" \
--header "Accept: application/json" \
--header "Idempotency-Key: $(uuidgen)"
For retries, reuse the original key instead of generating another UUID.
Response
200 OK. Illustrative values; IDs and positions will differ.
{
"data": {
"id": 42,
"deleted": true
}
}
Behavior and constraints
Deletes only unused custom definitions owned by this organization. System definitions, shared defaults, organization overrides, definitions referenced by assets or acquisitions, and definitions with recorded history or retained field values return 409. Checks include current asset conditions, decommissioning, drafts, and archived assets. Disable with visible: false instead. A successful deletion returns JSON, and retrying the same key replays that response even after deletion. Request bodies and query parameters are unsupported.
Errors
401 means the customer token is missing, invalid, expired, or revoked, or its creator is inactive. 403 means the required permission or administrator membership is missing. 404 means the definition is unavailable in the token’s organization, including a shared ID already overridden. 422 means invalid or unsupported input. 429 means the rate limit was reached. Errors and limits. 409 means conflicting idempotency-key reuse or a protected deletion.