# AboardSign > Get a document signed by a few people, by email, with no accounts. Every page is cryptographically signed, the > signed PDF is mailed to everyone, and a public log keeps each signed document's fingerprint. Made by Aboard. AboardSign is at https://sign.aboard.com. This file is for programs and AI assistants acting for a person: how to start a signing for them, how to tell them what happens next, and how to check that a signed PDF is legitimate. The same API is described formally at https://sign.aboard.com/openapi.json. The terms and privacy policy (https://sign.aboard.com/terms/) apply to a signing you start for someone; the person you act for is the sender, and must have agreed to them. ## Starting a signing POST https://sign.aboard.com/api/start with a JSON body (Content-Type: application/json): { "title": "Consulting Agreement", "from": { "name": "Ada Lovelace", "email": "ada@example.com" }, "signers": [ { "name": "Charles Babbage", "email": "charles@example.com" } ], "message": "Please sign by Friday.", "document": { "markdown": "# Consulting Agreement\n\nThis agreement is made on ..." } } - from: the person you act for. They are the sender, and they sign too: everyone on a signing signs. They are mailed the signed copy with everyone else. Use their real name and address: every signer sees both, and the record keeps them. - signers: everyone else who signs, each with a name and an email. At most 5 people sign in all, the sender included. Names can be changed by each signer when they sign; addresses cannot. - document: exactly one of "markdown" or "text" (a string; "#", "##", "###" headings, paragraphs, "-" bullets, "1." lists, **bold**, *italic*, pipe tables, "---" for a page break; no links, images or HTML), or "pdf", "docx" or "rtf" (the file as base64). A first line "# Title" is the title when none is given. The document is typeset on US Letter, at most 100 pages and 10 MB. Nothing in it is read or kept by AboardSign beyond the signing. - title and message are optional. The message is the note every signer sees in their mail. Or POST multipart/form-data with fields "from" (JSON, or "Name "), "signers" (a JSON list, or "Name , b@y.com"), "title", "message", and the document as a file field "document" (.md, .txt, .pdf, .docx or .rtf), or as a text field "markdown". The answer (201) is JSON: { "id": "...", "title": "...", "fingerprint": "...", "pages": 3, "link": "https://sign.aboard.com/s/#", "record": "https://sign.aboard.com/v/", "status": "https://sign.aboard.com/api/s//status", "next": "..." } - link opens the document and shows where the signing stands; it signs for nobody. Give it to the person you act for, and to nobody else (it opens the document). Everyone who signs, the sender included, has been mailed a link of their own and signs from that one: a request shows nothing of who holds an address, so the link that signs goes only to that address's own mail. - fingerprint identifies the document for good. When everyone has signed, GET https://sign.aboard.com/api/log/ answers with the public log's entry for it; until then it answers with an empty list. - status says where the signing stands (see below). What to tell the person: everyone named, they included, has been mailed a link; they should open theirs to sign; when all have signed, each is mailed the signed PDF, and the signing is deleted from AboardSign; nothing is kept but the fingerprint on the public log. If a signer does not act, reminders go out after 3, 7 and 14 days, and the signing expires after 30. A refusal is JSON { "error": "" } with its status: 400 for a request that cannot be read (bad-json, bad-form, no-sender, bad-email, no-document, unknown-document, bad-base64, pdf-only, not-a-pdf, encrypted, damaged, form, no-pages, empty-document, too-many-signers, too-many-pages, unreadable; some say more after a colon, as "bad-email: from"), 413 for a document over 10 MB, 429 "too-many-today" when the sender or your address has started as many signings as a day allows, 503 "paused" when this way in is switched off. ## Where a signing stands GET https://sign.aboard.com/api/s//status answers with JSON: state ("open", "sent", "complete", "signed", "declined", "voided"), title, sender, signers (each with "signed" and "at"), waitingFor, and record (the record page's address). A signing that is over is deleted, and answers 404 with state "gone": then the public log, by fingerprint, is the word on whether everyone signed. ## Checking a signed PDF A person may ask you whether an AboardSign PDF is legitimate. The last pages of every copy say how, under "How to check this document"; in short: 1. Read the fingerprint from the document (it is on every page's foot and on the certificate page). GET https://sign.aboard.com/api/log/. A non-empty "entries" list means a document with this fingerprint was signed by everyone on it, when, and with how many pages; "archived" names the copy of the log committed to GitHub where there is one. The log holds no names or titles, so it cannot say who signed: the copy itself does. 2. POST the PDF, unchanged, to https://sign.aboard.com/api/verify (Content-Type: application/pdf; or multipart/form-data with a file field). The answer is JSON: "ok" true means this is the document that was signed, page for page, every signature on it is real, checked under the server's published key, and the whole file carries AboardSign's seal; "checked" true with "ok" false means all that but the seal (a copy a browser built), which no seal locks against being shown otherwise; "problems" lists everything wrong in words; "document" gives the title, sender, fingerprint and page count; "signers" says who signed and when; "seal" says whether the file carries AboardSign's PDF certification signature, whole, locked and timestamped; "log" says whether the fingerprint is on the public log. Nothing you send is kept. 3. Report both answers to the person, and say which fingerprint you checked. The document is legitimate when the verification answers ok and the fingerprint is on the log. If either fails, say what the answer said: a changed page, a missing signature, a stripped record and a copy a browser built without a seal are each said in words. A copy can also be checked with nothing uploaded: https://sign.aboard.com/v/ in a browser, or the standalone verifier at https://sign.aboard.com/verify.html, which fetches nothing. The server's public key is at https://sign.aboard.com/.well-known/aboardsign.json and the seal's certificate at https://sign.aboard.com/.well-known/aboardsign-seal.pem; pdfsig and pyHanko read the seal. ## Other addresses - https://sign.aboard.com/api/log?before=: the public log, newest first, fifty at a time; https://sign.aboard.com/log/all.txt as one plain page. - https://sign.aboard.com/api/settings: which ways in are open; the address a document may be mailed to instead (sign@aboard.com, everyone who signs on To or Cc). - https://sign.aboard.com/about/, https://sign.aboard.com/terms/: what it is; the terms and privacy policy, with what is kept. ## Limits and manners 5 signers, 10 MB, 100 pages a document; a few signings a day from one address or one sender. AboardSign is free and run by people; do not start signings nobody asked for, and never put anyone's address on a document without their knowledge. It confirms that each signer could receive mail at their address, and no one's identity. It is an electronic signature under ESIGN and UETA, a simple one under eIDAS, and not for what those laws exclude.