Skip to main content
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.
  • 200 means the atomic rename completed. Successful result buckets have code: "ok", error_count: 0, and an empty errors array.
  • 409 means nothing was partially migrated. Detail codes include key conflicts, rename_busy, blockers, and stale_preview.
  • Pass attribute_id when 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 returns 409 stale_preview.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

key
string
required

Existing canonical Attribute key.

Body

application/json
new_key
string
required
Pattern: ^[a-zA-Z0-9][a-zA-Z0-9_/]*$
attribute_id
string<uuid>

Stable Attribute ID for retrying an uncertain rename outcome after the key may have changed.

expected_impact_revision
string

Optional optimistic-concurrency token. Most API clients should omit it; an outdated value returns 409 stale_preview.

Response

Atomic rename and all dependent migrations completed

success
boolean
required
partial
boolean
required
old_key
string
required
new_key
string
required
updated_count
integer
required
Required range: x >= 0
error_count
integer
required
attribute
object
required
Example:
results
object
required