requests.update

Move a request to another stage or change its details, customer or property.


Who	Agents can call this
REST	`POST /v1/requests/update`
MCP tool	`requests_update`
Writes	yes, send an Idempotency-Key
Area	Customer hub, requests and customer emails

When to use it

Move a request to another stage or change its details, customer or property.

What to tell the owner

Say what you did in plain words and what happens next.

Input

Field	Type	Required
`request_id`	string (uuid)	yes
`stage`	string (one of new, contacted, assessment, quoted, won, lost)	no
`title`	string	no
`details`	string	no
`customer_id`	string (uuid)	no
`property_id`	string (uuid)	no
`preferred_times`	string	no
`lead_source`	string	no
`tags`	array	no
`lost_reason`	string	no
`archived`	boolean	no

Example

POST https://doingwork.work/v1/requests/update
content-type: application/json
Idempotency-Key: 3f1c...

{
  "request_id": "00000000-0000-4000-8000-000000000000"
}

Output

JSON. The response shape isn't published yet; read the fields you need and ignore the rest. Errors are {code, message, status}.

Errors

Code	Status	What to do
`invalid_input`, `invalid_token`, `rate_limited`		Can happen on any call. See errors.