AssetCenter
/api/v1/people/{record}
Update a person
Update the supplied detail fields on an existing person.
Last updated
Request
PATCH / PUT /api/v1/people/{record}
Requires people:update. See token permissions. Every listed permission is required for this endpoint.
Send Authorization: Bearer YOUR_API_TOKEN and Accept: application/json. Send request bodies as JSON with Content-Type: application/json.
record is the numeric person ID in your token’s organization.
Request body
| Field | Type | Usage |
|---|---|---|
first_name |
string | Optional on update. Up to 255 characters; cannot be empty when supplied. |
last_name |
string | Optional on update. Up to 255 characters; cannot be empty when supplied. |
email |
string or null | Optional. Valid email address, up to 255 characters. |
title |
string or null | Optional. Job title, up to 255 characters. |
department |
string or null | Optional. Up to 255 characters. |
phone_number |
string or null | Optional. Up to 255 characters. |
is_external |
boolean | Optional. Whether this person belongs to an external organization. |
organization |
string or null | Optional. Up to 255 characters; used when is_external is true. |
Example
Set ASSETCENTER_API_TOKEN as described in the quick start. Replace example record and option IDs with values from your organization.
curl --request PATCH "https://my.assetcenter.app/api/v1/people/123" \
--header "Authorization: Bearer $ASSETCENTER_API_TOKEN" \
--header "Accept: application/json" \
--header "Content-Type: application/json" \
--data '{"department":"Operations"}'
Response
200 OK. Example response; IDs, values, and timestamps will differ in your organization.
{
"data": {
"id": 123,
"first_name": "Alex",
"last_name": "Morgan",
"email": "[email protected]",
"title": null,
"department": "Operations",
"phone_number": null,
"is_external": false,
"organization": null,
"status": "active",
"created_at": "2026-09-07T16:00:00.000000Z",
"updated_at": "2026-09-07T16:00:00.000000Z"
}
}
Behavior and constraints
PATCH and PUT both update only the supplied fields. Supply at least one writable field. Unknown fields, lifecycle status, assignments, and file uploads are rejected. These inventory updates have no idempotency replay protection.
Errors
401 means the token is missing, expired, revoked, or not a customer API token. 403 means a required permission or administrator access is missing. 404 means the record or child record is unavailable in this organization. 422 identifies invalid or unsupported input; inspect the errors object when present. 409 indicates a conflicting state or concurrent change; inspect the message and refresh the record before deciding how to proceed. 429 means a rate limit was reached. See error handling and rate limits.