Attributes
Rename an Attribute key and dependent data
Atomically renames an Attribute key and its supported dependent data. A blocked, conflicting, busy, or stale rename returns 409 without partial completion.
POST
Rename an Attribute key and dependent data
Atomic behavior
The handler previews the affected resources and then applies the key change and supported dependent migrations in one database operation.200means the atomic rename completed. Successful result buckets havecode: "ok",error_count: 0, and an emptyerrorsarray.409means nothing was partially migrated. Detail codes include key conflicts,rename_busy, blockers, andstale_preview.- Pass
attribute_idwhen retrying an uncertain request so the handler can identify the same Attribute even if its key already changed. - Most API clients should omit
expected_impact_revision. If you provide an outdated token, the handler returns409 stale_preview.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Existing canonical Attribute key.
Body
application/json
Pattern:
^[a-zA-Z0-9][a-zA-Z0-9_/]*$Stable Attribute ID for retrying an uncertain rename outcome after the key may have changed.
Optional optimistic-concurrency token. Most API clients should omit it; an outdated value returns 409 stale_preview.

