Change what is known about a person

PUT /people/{personId}

Every field is optional; a field sent replaces what was there (addresses is the whole set afterwards — an address without an id is new; one with an id not on the person is refused with 409 AddressNotFound; one sent with different details retires that version and mints a new id, since addresses are immutable so that what an order pinned never changes; an active address left out is retired), null clears an optional detail, and a changed email or phone is held to the same uniqueness rule as creation. An erased person cannot be changed (409 PersonErased). Appends crm.person-updated carrying the whole record, sealed, alongside changed — the names of the fields that actually moved, in the clear, so a timeline can say what happened without holding the key. Idempotent by content: a retry that says what the record already says appends nothing.

Access

Requires customers:write.

How scopes come from roles: Scopes and roles. Getting a token: Authentication and app tokens.

Retries

Idempotent by content: a retry that says what the record already says appends nothing.

Why every write carries a key: Idempotency and retries.

Facts appended

crm.person-updated

What a fact is: Facts and the journal.

AI agent tool

Agents call this as crm_update_person (CRM: Update person), in the crm toolset.

Connecting an agent: AI agents.

Example

curl

curl -X PUT 'https://crm.getmanifold.io/people/psn_01a1588a-0c41-7d2e-9a10-3b5c6d7e8f90' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{
  "phone": "+61 400 555 015"
}'

JavaScript (fetch)

const response = await fetch("https://crm.getmanifold.io/people/psn_01a1588a-0c41-7d2e-9a10-3b5c6d7e8f90", {
  method: "PUT",
  headers: { Authorization: `Bearer ${process.env.MANIFOLD_TOKEN}`, "Content-Type": "application/json" },
  body: JSON.stringify({
    "phone": "+61 400 555 015"
  }),
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const answer = await response.json();

Request body · application/json

{
  "phone": "+61 400 555 015"
}

Response · 200 · application/json

{
  "id": "psn_01a1588a-0c41-7d2e-9a10-3b5c6d7e8f90",
  "emailKey": "593c82fc1f2944d758cdd3ba99d3846467ec3417f394e5f47c7410b939a0a83c",
  "status": "active",
  "tags": [
    "trade"
  ],
  "roles": [
    "customer"
  ],
  "taxExempt": false,
  "emailMarketing": "subscribed",
  "smsMarketing": "not-subscribed",
  "profile": {
    "email": "priya.raman@harbourceramics.example",
    "firstName": "Priya",
    "lastName": "Raman",
    "phone": "+61 400 555 015",
    "locale": "en-AU",
    "addresses": [
      {
        "id": "adr_01a1588a-0c41-7d2e-9a10-4c6d7e8f9a01",
        "firstName": "Priya",
        "lastName": "Raman",
        "company": "Harbour Ceramics",
        "address1": "14 Kiln Street",
        "city": "Fremantle",
        "province": "Western Australia",
        "provinceCode": "WA",
        "country": "Australia",
        "countryCode": "AU",
        "zip": "6160",
        "retired": false
      }
    ]
  },
  "createdAt": "2026-10-20T09:00:00.000Z",
  "updatedAt": "2026-10-20T09:12:00.000Z"
}

The panel writes this call in other languages. It does not send it: Manifold's APIs do not take calls from a web page on another site, so run the call from your own code or terminal. The whole API as OpenAPI: crm-manager.openapi.json. Base URL https://crm.getmanifold.io.

Errors

Every refusal is a status and a JSON body whose _tag names it. A refused call changes nothing.

`401`

Refusal	What it means	What to do
`Unauthorized` reason	The token is missing, expired or not one Manifold issued.	Get a fresh token and send the call again.
`TokenAlreadyUsed` tokenId	A single-use app token was already spent.	Mint a new token for this call.

`402`

Refusal	What it means	What to do
`SubscriptionRequired` status	The organization's subscription has lapsed, so writes are refused.	An owner settles billing. Reads still work meanwhile.

`403`

Refusal	What it means	What to do
`TenantRequired` userId	The token names no organization.	Choose the organization, then get a new token.
`ScopeRequired` required	The token's roles do not grant the scope this call needs.	Ask an owner or admin for a role that grants it.

`404`

Refusal	What it means	What to do
`PersonNotFound` personId	No such record in this organization.	Check the id in the path or the body.

`409`

Refusal	What it means	What to do
`PersonErased` personId	The person was erased at their request and holds no details.	Nothing can change an erased person.
`PersonEmailConflict` personId	Another person already has this email address.	Use that person's record.
`PersonPhoneConflict` personId	Another person already has this phone number.	Use that person's record.
`AddressNotFound` personId, addressId	The person has no address with that id.	Use an `addressId` from the person's record.
`MirroredFromSource` source	This area is fed by your source system until the organization goes live.	Make the change in the source system, or go live first.

`503`

Refusal	What it means	What to do
`RequestLogUnavailable` tokenId, reason	The service could not record the request, so it did nothing.	Send the same request again shortly.

How refusals work everywhere: Errors.

Used in

A person, a supplier, and a right-to-erasure request, step 6: Correct the person's details