# Update an Apple Messages for Business record

`PATCH /v1/amb/businesses/{business_id}`

Changes your workspace's Apple Messages for Business record. Fields you
omit are left as they are.

Sending `apple_business_id` identifies the draft but does not submit it.
Create a submission with all three evidence attachments when the record
is ready for review.

## Code samples

**TypeScript**

```ts
const result = await bird.amb.businesses.update(
  "abz_01krdgeqcxet5s7t44vh8rt9mg",
  { display_name: "Acme Support" },
);
console.log(result);
```

Examples: [TypeScript](/docs/api/reference/update-amb-business.ts.md) · [Python](/docs/api/reference/update-amb-business.py.md) · [Go](/docs/api/reference/update-amb-business.go.md) · [PHP](/docs/api/reference/update-amb-business.php.md) · [CLI](/docs/api/reference/update-amb-business.cli.md) · [MCP](/docs/api/reference/update-amb-business.mcp.md) · [cURL](/docs/api/reference/update-amb-business.curl.md)

## Example response `200`

```json
{
  "id": "abz_01krdgeqcxet5s7t44vh8rt9mg",
  "apple_business_id": "b52d6267-2b62-4f8a-8842-0533d0f1dc07",
  "display_name": "Acme Retail",
  "status": "approved",
  "status_reason": null,
  "msp_app": "eu1",
  "invitations_enabled": false,
  "created_at": "2026-08-20T09:14:52Z",
  "updated_at": "2026-08-25T16:42:01Z",
  "next": [
    {
      "kind": "operation"
    }
  ]
}
```

## Path parameters

- `business_id` (string): ID of the Apple Messages for Business record, as returned by the business list.

## Request body

- `display_name` (string): The brand name shown for this business record inside Bird.
- `apple_business_id` (string): The Business ID Apple issued for this brand. Accepted only while the business is `draft`, or to correct a missing or invalid legacy ID on a `rejected` business. Updating it does not submit the business.

## Response body

- `id` (string, required): Unique identifier for the business record.
- `apple_business_id` (nullable string, required): The Apple Business ID stored for this brand. Null until supplied. New values must be UUIDs; legacy records can contain a non-UUID identifier until corrected. Supplying or correcting the identifier leaves the status unchanged; an evidence submission moves the record to `submitted`.
- `display_name` (string, required): The brand name shown for this business record inside Bird. This is not the name Apple shows to customers; that name comes from the Apple Business Register account behind the Business ID.
- `status` (string, required)

  Where the business record stands with Apple.

  Possible values: `draft`, `submitted`, `in_review`, `approved`, `rejected`, `suspended`
- `status_reason` (nullable string, required): Free-text detail behind `status`, such as why Apple's review ended in `rejected`. Null when Bird has recorded no detail for the current status.
- `msp_app` (string, required)

  The regional Messaging Service Provider application this business is registered under.

  Possible values: `eu1`, `us1`
- `invitations_enabled` (boolean, required): Whether this business can send invitations. Apple grants invitation access separately from approving the business itself, so this can be false on an `approved` business.
- `created_at` (string, required): When the business record was created.
- `updated_at` (string, required): When the business record was last changed.
- `next` (array of object): Onboarding actions computed from the business status and Apple Business ID. Present on create, update and single-business reads; omitted on lists. Approved businesses have no onboarding action. Evidence readiness is not inferred from this record; prepare and upload the required files before submission.
- `next.kind` (string, required)

  What you do about this step.

  - `operation`: call the operation named in `operation`, then
    read again.
  - `external`: act somewhere this API does not reach, then read
    again.
  - `wait`: nothing is asked of you, so read again later.
  - `terminal`: nothing you do resolves this, so stop retrying.

  Tolerate a value you do not recognize: show the `description` and
  offer no action.

  Possible values (may grow over time): `operation`, `external`, `wait`, `terminal`
- `next.description` (string, required): A short, human-readable label for the step, suitable for display.
- `next.operation` (string): The operationId to call. Present only when `kind` is `operation`. The operation's own schema says how to call it; this says only which one, and what to address it with.
- `next.params` (object): The parameters that address the operation, by name: `{"sender_id": "…"}` for an operation on `/v1/sms/senders/{sender_id}/requirements`. A parameter the operation takes in its query string is given the same way, so an operation addressed as `?subject_id=` carries `{"subject_id": "…"}`. Every parameter the call needs is here, whether its value came from the thing you were acting on or is fixed for this step, so you can make the call from this object alone. Present only when `kind` is `operation` and the operation names a subject. A request body, when the operation takes one, is described by the operation's own schema and never appears here.
- `next.url` (string): A URL to open. Present only when `kind` is `external`, and only when the step has one. An external step whose `description` says to go and do something with no URL to open is normal.

## Related resources

- [Should I use a Bird SDK or call the API directly?](/explained/platform/should-i-use-an-sdk-or-call-the-api-directly) (answer)
- [Build your first integration](/learn/paths/integration) (course)
- [Send your first email](/docs/get-started/send-your-first-email) (docs)

[Get an implementation brief](/learn/workspace?topic=api-basics)