signatures.sign

Sign a document after reading it, typing your name and agreeing to sign electronically. Hosted page only; agents can never sign.


Who	Hosted page only (a person does it in the browser)
REST	`POST /v1/signatures/sign`
MCP tool	Not an MCP tool
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

Send the person the link. They finish this step themselves on the page; you never do it for them.

Input

Field	Type	Required
`t`	string	yes
`document_sha256`	string	yes
`signer_name`	string	yes
`esign_consent`	string (one of yes)	yes

Example

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

{
  "t": "...",
  "document_sha256": "...",
  "signer_name": "...",
  "esign_consent": "yes"
}

Output

Field	Type	Always there
`signature_id`	string (uuid)	yes
`signature_request_id`	string (uuid)	yes
`document_sha256`	string	yes
`consent_sha256`	string	yes
`signed_at`	string (date-time)	yes

{
  "signature_id": "00000000-0000-4000-8000-000000000000",
  "signature_request_id": "00000000-0000-4000-8000-000000000000",
  "document_sha256": "...",
  "consent_sha256": "...",
  "signed_at": "..."
}

Errors

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