signatures.request

Ask someone to sign a document on a hosted page, and get the signing link to give them. kind contract: text is the agreement exactly as the shop wrote it (Doing Work never writes contract or legal wording). kind job_document: a stored job PDF (documents.list). The signer signs in, reads it, types their name and agrees to sign electronically. Agents can never sign.


Who	Agents can call this
REST	`POST /v1/signatures`
MCP tool	`signatures_request`
Writes	yes, send an Idempotency-Key
Area	Field work (checklists, forms, time, notes, change orders, subcontractors)

When to use it

Ask a customer, or someone in the shop, to sign a document: contract text you supply (for example a service agreement) or a PDF already stored on the job. signatures.request returns a sign_url on the hosted pages; send it to the signer yourself.

What to tell the owner

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

Input

Field	Type	Required
`kind`	string (one of contract, job_document)	yes
`job_id`	string (uuid)	no
`customer_id`	string (uuid)	no
`title`	string	yes
`text`	string	no
`document_id`	string (uuid)	no
`signer_role`	string (one of customer, member)	no
`signer_email`	string	no
`link_days`	integer	no

Example

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

{
  "kind": "contract",
  "title": "..."
}

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.