PearSign API documentation

A REST API for electronic signatures: create and send envelopes for signature, track their status, download completed documents with their audit trail, and receive webhooks when something changes. Authentication is a bearer token over HTTPS on every request.

1. Create an API key in Settings → API Keys. Test keys start with ps_test_, live keys with ps_live_.
2. Send the key as a bearer token in the Authorization header. All requests require HTTPS.
3. Handle standard HTTP status codes. Rate-limit headers are included on every response.

The API is organised into nine resource groups: Envelopes for creating and sending documents out for signature, Documents for retrieving completed files, Templates and Fields for reusable documents and the positions signers fill in, FusionForms for guided fill-out flows, Webhooks for delivery of events as they happen, Audit for the tamper-evident trail behind a signature, and Tenant management and Public API for organisation and unauthenticated surfaces.

The full machine-readable specification is published at /api/v1/openapi.json. Loading the interactive explorer…

Elsewhere on PearSign: the product, pricing, how signatures are secured and the guides.