---
title: "Update an identity name"
method: PATCH
path: "/v1/compliance/identities/{identity_id}"
tags: ["compliance"]
---

# Update an identity name

`PATCH /v1/compliance/identities/{identity_id}`

## Request

- Base URL: `https://us1.platform.bird.com`
- URL: `https://us1.platform.bird.com/v1/compliance/identities/{identity_id}`
- Auth: one of:
  - HTTP bearer
  - API key in cookie `bird_session`

Renames the party.

Only the name is yours to set. The business details are filled in from your
registrations: each single-value answer you file about the party is written
back onto it, whatever the verdict. Documents and multi-value answers are
not kept on the party. To correct one, send the new value on a registration.

Renaming does not disturb registrations already filed with this party. A verdict
already given stands against the details it was given for.

## Headers

- `Idempotency-Key` string
- `X-Workspace-Id` string
- `X-Organization-Id` string

## Request body

- ComplianceIdentityUpdate: Renames the party. Single-value identity answers are filled in when you submit or resupply a registration, regardless of its review outcome. Edit those answers through the registration.
  - `name` string, required: What you call this party. Yours to choose; it is never sent to a carrier.

## Response `200`

The updated identity.

- ComplianceIdentity: A party you register on behalf of: your own business, or one of your clients. Reusing an identity across registrations is what stops you retyping the same business details for every country, and lets a fact reviewed once stand for the registrations that follow.
  - `id` string, required
  - `name` string, required: What you call this party. Yours to choose; it is never sent to a carrier.
  - `answers` object, required: The business details this party has supplied, keyed by requirement. Filled in for you: a single-value detail lands here the moment you file it on one of your registrations, so the next one prefills it rather than asking again. Only requirements a country marks as being about the party appear; anything about a specific sender is asked fresh each time.
  - `created_at` string, date-time, required
  - `updated_at` string, date-time, required

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Insufficient permissions
- `404`: Resource not found
- `409`: Resource conflict
- `422`: Validation failed
- `429`: Rate limit exceeded
- `500`: Internal server error
- `503`: The service is temporarily unavailable. If `Retry-After` is present, wait for that delay before retrying; otherwise, retry with exponential backoff. Reuse the same idempotency key and request when retrying a mutation.

## Changes

- **2026-10-20** `a1977645a499`: 1 info
  - endpoint added
- **2026-10-20** `6cec81ac4862`: 1 breaking
  - api path removed without deprecation
- **2026-10-20** `3e2a50466454`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/messagebird/apis/bird-api/changes/v1/compliance/identities/:identity_id/patch.md)

---

[API](https://skmtc.dev/messagebird/apis/bird-api.md) · [All operations](https://skmtc.dev/messagebird/apis/bird-api/llms.txt) · [OpenAPI document](https://skmtc.dev/messagebird/apis/bird-api/revisions/483bb7bfdc89?raw)