---
title: changes.send | Doing Work API
description: Owner or office: ask the customer to approve a change order. Doing Work writes the document (the lines, totals and the job's total before and after) and re
url: https://doingwork.work/docs/reference/changes-send/
---

# changes.send

Owner or office: ask the customer to approve a change order. Doing Work writes the document (the lines, totals and the job's total before and after) and returns a single-use sign_url for the agent to deliver; the customer signs it on a hosted page and the change order becomes approved. To send again after the request was cancelled, call this again; for a fresh link on an open request use signatures.newLink.

|  |  |
|---|---|
| Who | Agents can call this |
| REST | `POST /v1/change-orders/send` |
| MCP tool | `changes_send` |
| Writes | yes, send an Idempotency-Key |
| Area | [Field work (checklists, forms, time, notes, change orders, subcontractors)](https://doingwork.work/docs/reference/#field-work-checklists-forms-time-notes-change-orders-subcontractors) |

## When to use it

A change order is a priced change to a job's scope: extra work, or a credit for work taken out. A worker writes the lines (changes.create; never fill prices in yourself).

## What to tell the owner

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

## Input

| Field | Type | Required |
|---|---|---|
| `change_order_id` | string (uuid) | yes |
| `signer_email` | string | no |
| `link_days` | integer | no |

## Example

```http
POST https://doingwork.work/v1/change-orders/send
content-type: application/json
Idempotency-Key: 3f1c...

{
  "change_order_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](https://doingwork.work/docs/errors/). |