{"service":"Pro Sign AI","summary":"API-first electronic signature service. An AI agent can register for a person in seconds: send the person's name, email and the permissions you need; you get your token and its ID back immediately. The token does nothing until the person approves and signs on a one-page form in their browser (no typing); then it goes live with exactly the approved permissions. Then you send PDFs for legally valid e-signature, get webhooks, and download sealed results.","register":{"step1":{"method":"POST","url":"https://sign.prodevgroup.com/api/v1/agent-access/requests","auth":"none","body":{"email":"the person you act for, who will own the key (required)","name":"the person's name (required), used in the greeting and for their account","organizationName":"their company (optional, used if they have no account yet)","agentName":"how you, the assistant, introduce yourself; the person sees this in the email and on the approval page, e.g. \"Lori (Pro Building assistant)\" (optional; default \"'s AI assistant\")","purpose":"one sentence on why (optional)","requestedScopes":["documents:read","documents:write","documents:send","webhooks:manage"],"note":"your own wording to the person (optional)","validForHours":"optional: ask for a TEMPORARY token that stops on its own this many hours after approval (1 to 168, one week). Use it when you cannot store a secret safely (chat transcript, no credential store). \"temporary\": true alone means 24 hours."},"response":"apiKey (your token, shown once), tokenId (how you refer to it later), tokenStatus PENDING, and pollUrl (keep it; it contains a secret)","example":"curl -X POST https://sign.prodevgroup.com/api/v1/agent-access/requests -H 'content-type: application/json' -d '{\"email\":\"jane@example.com\",\"name\":\"Jane Doe\",\"agentName\":\"Jane\\u2019s assistant\",\"purpose\":\"Send contracts for signature\",\"requestedScopes\":[\"documents:read\",\"documents:write\",\"documents:send\"]}'"},"step2":"The person gets an email with one page: their name (editable), a permission table (Permission | Asked | Approve | Deny) prefilled from your request, the electronic-signing consent and a signature pad. They tap Approve and sign. Nothing is granted until then.","step3":"Until then every call with your token answers 403 token_pending_approval. Poll pollUrl every 30 to 60 seconds (tokenStatus becomes ACTIVE, status APPROVED), or simply retry; DECLINED or EXPIRED (7 days) means no.","step4":"Once approved the same token is live with exactly the permissions the person approved (they may approve fewer than you asked). Nothing to pick up.","step5":"Use the token as \"Authorization: Bearer psk_live_...\" on https://sign.prodevgroup.com/api/v1 or as the bearer on the MCP endpoint https://sign.prodevgroup.com/mcp. Keep the tokenId: it is how you refer to the token later (never send the token itself).","changePermissions":"POST https://sign.prodevgroup.com/api/v1/agent-access/changes with your key and the new requestedScopes; the person re-approves and re-signs; your key's permissions change in place.","actions":{"new_account":"first token for a person who has no account yet; token returned now, live after approve + sign","new_token":"another token on an existing account, for a different agent or application; token returned now, live after approve + sign","rotate_token":"fresh token with the same permissions returned now; one-tap confirm makes it live and stops the old one; needs tokenId","update_permissions":"change what a token may do; needs tokenId and requestedScopes (approve + sign)","remove_tokens":"revoke tokens; tokenIds, or omit to let the person pick (one-tap confirm)","create_company":"create a company with the person as owner; needs companyName (+ optional companyDetails). You get the company code (co_...) at once; the company and your company-bound token go live when the owner signs","join_company":"join an existing company for the person; needs companyId. The person signs for your company-bound token, and a company admin approves the membership with one tap; the token goes live when both are done","transfer_company":"the company owner signs over control to another active member; needs companyId and newOwnerEmail","companies":"A person has a personal workspace and can belong to any number of companies with the same email. Every documents/templates/webhooks call takes companyId (query or body) to run in that company; without it the call is personal. Company templates and documents are visible to company admins; personal ones are not. If the person is not an active member you get 403 not_a_member; an unknown code gives 404 no_company. GET /me lists the workspaces.","note":"Every action emails the person a one-page form. Default action is new_account for an unknown email, otherwise new_token."},"temporaryKeys":"If your key would end up in a chat transcript or you have nowhere safe to keep it, ask for a temporary one: add \"validForHours\": 24 (any whole number from 1 to 168) to a new_account or new_token request. The token works for exactly that long after the person approves, then stops on its own (calls answer 401 token_expired). Ask again as often as you like: the first temporary token needs the signed authorization like any other; every later one is a one-tap approval email with no signature, so it costs the person almost nothing. The response and pollUrl carry temporary, validForHours and tokenExpiresAt."},"permissions":[{"scope":"documents:read","title":"See documents and their status","description":"List documents, read who has signed, download completed files, audit trails and certificates."},{"scope":"documents:write","title":"Prepare documents","description":"Upload PDFs, add signers and fields, edit drafts, delete drafts."},{"scope":"documents:send","title":"Send for signature","description":"Send documents to people in your name, send reminders, issue signing links, void documents."},{"scope":"templates:read","title":"Use templates","description":"See and use your saved templates."},{"scope":"templates:write","title":"Manage templates","description":"Create and delete templates."},{"scope":"webhooks:manage","title":"Receive event notifications","description":"Register web addresses that get notified when documents are viewed, signed or completed."},{"scope":"admin","title":"Full control","description":"Everything above, plus managing members, other people's keys and organization settings."}],"afterRegistering":{"docs":"https://sign.prodevgroup.com/api/v1/docs","openapi":"https://sign.prodevgroup.com/api/v1/openapi.json","mcp":"https://sign.prodevgroup.com/mcp","sendingTips":["No vision and a PDF with no signature lines (an invoice, a letter)? Add \"signaturePage\" to POST /documents: you write the title and the statement, the server appends a page with a block per signer (signature line, date line, printed name, optional title) and places the fields itself; the response carries signaturePageText so you can check it. Example: {\"enabled\":true,\"title\":\"Acknowledgment of Receipt\",\"statement\":\"By signing below, I acknowledge that I received and reviewed Final Invoice PB-2026-KEN-FINAL dated October 12, 2026.\",\"blocks\":[{\"recipient\":1,\"label\":\"Homeowner\",\"printedName\":\"Jason Kendrick\",\"fields\":[\"signature\",\"date\"],\"align\":\"left\"},{\"recipient\":2,\"label\":\"Homeowner\",\"printedName\":\"Christina Kendrick\"}]}.","Put anchor tags in your PDF ({{signature:1}}, {{date:1}}, {{name:1}}, {{text:1:Policy number}}, {{checkbox:1}}) and set useAnchors:true; no coordinates needed. Add a last part left, center or right to align inside the box ({{signature:1:right}}); fields by coordinates take \"align\".","Several PDFs for the same people? POST /packets with a documents list (each with its own recipients and fields). Every signer gets one link for all of them, consents once, sees \"1/3 complete\", and moves to the next document automatically. orderLocked:true forces the order; the read-only link covers the whole packet.","Something to show but not sign (an invoice, an exhibit)? Add it as an attachment: in a packet a document with \"attachment\": true, or on POST /documents an \"attachments\" list (that turns the request into a packet behind the scenes; the response is still the document, with packet.id). Signers must open it; \"acknowledge\": \"sign\" or \"initial\" appends a receipt sheet instead. By default a packet with an attachment ends with a sealed Packet Acknowledgment: one signature per signer, every document listed with its SHA-256, always the last step. \"acknowledgment\": true/false overrides; GET /settings and PATCH /settings hold the workspace rule (always, attachments, never). When a packet completes, each person gets one \"Packet completed\" email (no per-document emails): the whole packet as one sealed PDF (every document followed by its certificate, then the packet audit; GET /packets/{id}/file, attached when small enough), a status page with per-document downloads, and their read link for an AI assistant. A review-only attachment also ends up sealed and timestamped, with a review record of who opened it. \"signedNotices\" in /settings (standalone by default) says whether the sender gets a \"Signed by X\" email per signature outside packets.","POST /documents/{id}/recipients/{rid}/link returns a signing link, a read-only link the signer can hand to their own AI, and a ready-to-send message you can personalize with note or messageTemplate.","Register a webhook to be told when a document is viewed, signed, declined or completed; or poll GET /documents/{id}.","GET /documents/{id}/text returns the document text so you can read it without vision."]},"signatureSpots":"Place fields without vision. GET /documents/{id}/signature-spots scans the PDF for signature, initials, date, printed-name and title lines (labels such as SIGNATURE, SIGN HERE, BY:, DATE, INITIALS, PRINTED NAME, TITLE; drawn lines; runs of underscores) and returns a numbered list, each with a plain-English description such as \"Signature line above 'Christina Kendrick / PRINTED NAME' in the block labeled 'Homeowner'\", the paired date spot, and a ready box above the line (26pt for a signature, 18pt for a date). Lines that already carry printed text are skipped. Give each recipient fields like [{\"spot\": 1}, {\"spot\": 2}] instead of coordinates; the server sizes them. Fastest path: POST /documents with \"detectSpots\": true (it returns signatureSpots and never sends), choose spots, PATCH /documents/{id} with recipients, then POST /documents/{id}/send. Spots work in templates too ({\"spot\": n, \"roleOrder\": r}).","signaturePage":"Generated signature page, for any PDF and no coordinates: \"signaturePage\": { \"enabled\": true, \"title\": \"Acknowledgment of Receipt\" (default \"Signatures\"), \"statement\": \"...plain text, blank lines become paragraphs, max 3000 characters...\", \"blocks\": [ { \"recipient\": 1, \"label\": \"Homeowner\", \"printedName\": \"Jason Kendrick\", \"title\": null, \"fields\": [\"signature\",\"date\"], \"align\": \"left\" }, ... ], \"layout\": \"stacked\" | \"two-column\" } on POST /documents, on each document of POST /packets, and on PATCH /documents/{id} (DRAFT; enabled:false removes it). \"recipient\" is the recipient order number; allowed fields: signature, initials, date, name, title, text: