Developers

The integration and automation surfaces.

A REST API, an MCP server, webhooks, and first-class agent participation. Bearer-token auth throughout. Agents and humans using the same protocols.

Code

# Authenticate with a Personal Access Token and create an agreement
 
curl -X POST https://api.allsign.app/agreements \
  -H "Authorization: Bearer <your-pat>" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Q3 Engineering Charter",
    "intent": "binding"
  }'
 
# {
#   "ref": "agr_01jx7kp9fge4dr3tz0wbmd",
#   "name": "Q3 Engineering Charter",
#   "intent": "binding",
#   "created_at": "2026-06-26T14:30:00Z",
#   "created_by": { "ref": "per_01jw9...", "name": "Al Newkirk" }
# }

Six ways to integrate.

Full lifecycle access: create, negotiate, sign, and audit agreements programmatically. Human actors and AI agents use the same endpoints.

REST API

Full range of operations for agreements, sections, terms, revisions, decisions, signatures, participants, and attachments. Bearer-token auth. All IDs are UUIDs. Paginated list endpoints throughout.

MCP Server

Connect AI agents to AllSign via the Model Context Protocol. Agents receive agreement context and act as first-class participants: comment, negotiate, decide, and sign.

Webhooks

Subscribe to lifecycle events: agreement created, term accepted or rejected, participant added, signature completed, agreement executed. Payloads include the full resource models.

Agent Participation

Register named agents with long-lived API keys. Invite them to agreements by UUID, no email address required. Agents participate using the same roles as humans: Author, Editor, Signer, Viewer, or Commentor.

Personal Access Tokens

Automate on behalf of your own account. PATs inherit full creator access. Generated once, shown once, revocable from Settings. Audit attribution traces to the issuing human actor.

Applications

Register named API client identities (integrations, services, CI systems). Applications authenticate with a rotatable API key. Agent Applications additionally provision a backing agent actor for lifecycle participation.

Go deeper.

The API and MCP servers have dedicated reference pages with endpoint details, data models, and usage examples.

REST API

Agreements as structured data.

Full endpoint reference for agreements, participants, terms, revisions, decisions, signatures, and audit events. Noun-based resource paths. Paginated lists. UUIDs throughout.

View API reference

MCP Server

Agents as participants.

Connect any MCP-compatible agent to AllSign. Agents get agreement context via tools and participate in the lifecycle with the same capabilities as human signers.

View MCP guide