Skip to content
kunal priyadarshi edited this page Oct 3, 2026 · 5 revisions

graphsign.ink documentation

Prepare agreements, collect signatures, and check the authenticity of completed documents. This documentation explains the application in everyday language and provides a separate reference for developers.

New here? Start with Getting Started, then follow Send Your First Agreement. If you received a signing invitation, go directly to Sign an Agreement.

Find the help you need

I want to… Read this guide
Create an account and find my way around Getting Started
Prepare and send my first document Send Your First Agreement
Upload, search, clone, archive, or download agreements Agreement Management
Add signatures, dates, and other fillable fields Document Editor and Fields
Request approval, choose signing order, or send a reminder Workflow Engine and Signer Portal
Sign or decline a document sent to me Sign an Agreement
Reuse a document layout Template Management
Invite colleagues and manage a workspace Organization and Tenancy
Change my profile, password, MFA, or session preferences Authentication and Identity
Check a signed document Cryptographic Signing and Verification
Connect another application Webhooks and REST API Integration
Look up endpoints and request formats REST API Reference
Understand records and safe handling Security and Audit Trail
Resolve an error or unfamiliar term Troubleshooting · Glossary

How an agreement moves through the system

  1. Prepare: upload a document, write one, or start from a template.
  2. Place fields: tell each recipient where to sign and what information to enter.
  3. Review: request internal approval when your process needs it.
  4. Send: select recipients, signing order, and an optional expiry date.
  5. Sign: recipients open their private invitation, review the document, and complete their assigned fields.
  6. Retain and verify: download the completed file, retain the supporting records, and check its verification result.

An agreement is the document and its workflow. The integration API calls the same underlying record a document. A template is a reusable starting point; creating an agreement from it produces a separate draft.

What is available

The current application includes PDF and Markdown editing, recipient fields, internal review, parallel and sequential signing, signer email verification, templates, search and filter presets, version history, workspace membership and roles, profile and session settings, authenticator MFA, certificates, public verification, document REST endpoints, and webhook subscription management.

Availability depends on your role, workspace type, enabled features, and deployment configuration. Read Feature Availability for important differences between visible controls, implemented APIs, and services requiring operator configuration.

Use the application, browse the source project, or report an issue. Keep private documents, credentials, and signing links out of public issue reports.

Clone this wiki locally