Permanently delete an attribute description from the system
DELETE/v2/attribute-descriptions/:lookupKey/:lookupValue
Remove an attribute description and all its configuration permanently from the system.
This operation will delete the attribute description schema including all metadata and configuration settings. This is a destructive operation that cannot be undone.
Warning: Deleting an attribute description may affect existing attributes that depend on this description. Ensure no active attributes are using this description before deletion.
The deletion process:
- Removes the attribute description record completely
- Cleans up associated metadata and configuration
- Maintains system integrity and consistency
- Cannot be reversed once completed
Request
Responses
- 200
- 400
- 401
- 404
- 409
- 500
- 503
Successfully deleted the attribute description
Invalid request parameters or validation errors
Authentication required - Invalid or missing OAuth2 token
Attribute description not found with the specified criteria
The attribute description is still in use and cannot be deleted. There is no override — remove whatever references it first.
The body carries the per-source breakdown that justifies the refusal, so a client can show what is holding the description rather than string-matching the message. usage.carts and usage.tenders count affected CARTS and TENDERS (not individual matching rows), and are always 0 for a class other than ORDER / ORDER_ITEM.
attributeClass is reported as the enum NAME — ORDER, ORDER_ITEM, PRODUCT — which is the form the GraphQL API uses for this class everywhere. Note it is NOT the lowercase form the resourceType query parameter takes (order, orderItem, product).
Internal server error occurred while deleting the attribute description.
Safe to retry: the usage check runs before the delete transaction and only ever reads, so a failure here leaves the tenant exactly as it was.
Whether the description is still in use could not be determined because cart-service or tender-service was unreachable. The delete fails closed and nothing was changed; retry once the dependency recovers. Only ORDER and ORDER_ITEM descriptions are probed against those services.