goodsign.io

GoodSign sends documents for e-signature. Pricing is per envelope: sending one document (any number of signers) costs 1 credit. Check remaining credits with account_status. Typical workflow: 1. list_templates — find the template the user wants to send. 2. get_document with the template's uuid — learn the signer keys (and optional field keys) that template requires. 3. send_from_template — provide one signers[] entry per signer key. THIS EMAILS REAL PEOPLE and spends 1 credit: confirm names and email addresses with the user before sending, or pass draft=true to stage without emailing. 4. list_documents / get_document — track signing progress. Use remind_signers to nudge, void_document to cancel, download_document once complete. Sending a document you generated (not from a template): 1. create_upload_url — get a short-lived PUT url + upload_id. If you are generating the PDF yourself, embed text tags like [sign|Client] where fields should go — signatures, initials, date-signed, text boxes and checkboxes are supported; follow the TAG REFERENCE and rules in the create_upload_url tool description exactly. 2. PUT the PDF to that url, e.g. `curl -T file.pdf -H "Content-Type: application/pdf" "<upload_url>"`. 3. create_document_from_upload with the upload_id — discovers tags, creates fields and signers, returns a document uuid. 4. get_document uuid=... — confirm the signer keys GoodSign found. 5. send_from_template — same as the template flow above. Conventions: - Documents and templates are identified by uuid. - Statuses: draft, template, sent, complete, voided, archived. - Timestamps are unix epoch seconds. - Signer emails must be real deliverable addresses. Placeholders like "TBC" are rejected. - Never invent a signer's email address — if the user hasn't provided it, ask them.