Delete an asset category

Request#

DELETE /api/v1/asset-categories/{category}

Requires asset-categories:delete. The token creator must remain an active administrator of the token’s organization. Category permissions.

Send Authorization: Bearer YOUR_API_TOKEN and Accept: application/json.

category is the numeric ID of an asset category in the token’s organization. Subscription categories are unavailable here.

Query parameters#

This endpoint does not use query parameters.

Request body#

Do not send a request body.

Requires Idempotency-Key. Generate one key per action and keep it for retries. Successful responses are remembered for 24 hours per token. Idempotency and retries.

Example#

Set ASSETCENTER_API_TOKEN as described in the quick start. Replace example IDs with values from your organization. For a retry, reuse the original key instead of generating another UUID.

curl --request DELETE "https://my.assetcenter.app/api/v1/asset-categories/7" \
  --header "Authorization: Bearer $ASSETCENTER_API_TOKEN" \
  --header "Accept: application/json" \
  --header "Idempotency-Key: $(uuidgen)"

Response#

200 OK. Illustrative response; IDs and values will differ.

{
  "data": {
    "id": 7,
    "deleted": true
  }
}

Behavior and constraints#

Deletion permanently removes the category and its unused custom-field definitions. It returns 409 if any asset uses the category, including archived or decommissioned assets, or if a field retains populated values from an asset moved to another category. Empty placeholder rows do not block deletion. This operation never deletes assets. Check can_delete in the category response; the server checks the constraint again when deleting.

Errors#

401 means the customer bearer token is missing, expired, revoked, or invalid. 403 means the required permission is missing or the token creator is no longer an active organization administrator. 404 means the category or field is unavailable in this organization. 422 identifies invalid or unsupported input. 429 means a rate limit was reached. Error handling and rate limits. 409 means conflicting key reuse or a data constraint described above. Successful deletes return JSON and can replay after the target is gone.