Overview

Authentisign API Documentation

Intro — What can be done with this API

The Authentisign API lets your software securely create, send, and manage e‑signature workflows end‑to‑end: build signings, add participants, deep‑link users into the designer, and retrieve executed documents and certificates. It supports turnkey “fill‑and‑send” flows, branded email controls, and post‑completion artifact retrieval for compliance and archival. Typical adopters are real estate platforms, brokerages, and proptech vendors embedding e‑sign inside CRMs, transaction systems, and consumer apps.

Common Use Cases

  • Push‑button “create, fill, and send” packages from your app

    • POST /api/v2/signings/fill-and-send-documents (multipart: Files, Fields, Participants, ordering, reminders, callback URL)

  • Deep‑link straight into the signing designer (SSO jump)

    • GET /api/v3/users/{userId}/sso/signing/{signingId}

  • Add carbon‑copy recipients in bulk

    • POST /api/v1/ccs/batch
    • POST /api/v3/users/{userId}/signings/ccs/batch

  • Pull completed artifacts for storage/compliance

    • Final combined package URL: GET /api/v1/signings/{signingId}/documents/s/url
    • Latest signed doc URL: GET /api/v1/signings/{signingId}/documents/ls (and /ls/url)
    • Signing certificate: GET /api/v1/signings/{signingId}/documents/sc
    • Original/final by encrypted document id: GET /api/v1/documents/{encryptedDocumentId}/o and /d (+ /o/url)

  • Show status for dashboards

    • Get a signing: GET /api/v1/signings/{id}
    • List CCs: GET /api/v1/signings/{signingId}/ccs
    • List deleted signings: GET /api/v3/users/{userId}/signings/deleted

  • Keep outbound email branding consistent

    • POST /api/v1/accounts/email-signature