Overview
Sealpost is an API-first e-signature service. You upload a PDF, create an envelope with recipients and field positions, and Sealpost takes it from there: each signer gets one email link, and when the last person signs you get back a sealed PDF and its record of events as JSON.
What you can call today
Section titled “What you can call today”| Area | Endpoints | Status |
|---|---|---|
| Connectivity and identity | GET /ping, GET /me |
Live |
| API keys | create, list, rotate, revoke | Live |
| Request log | GET /requests |
Live |
| Files | upload (multipart, URL, base64, presigned), status | Live |
| Envelopes | create a draft, read it back | Live |
| Sending, signing, sealing, webhooks | Coming next |
Everything is in the API reference, generated from the same OpenAPI contract the service is built from. The raw contract is at /openapi.yaml.
The basics
Section titled “The basics”- Base URL:
https://api.sealpost.app/v1 - Authentication:
Authorization: Bearer sk_test_…orsk_live_…. See Authentication and keys. - Test mode: a test key never sends real email or bills anything. See Test mode.
- Errors:
application/problem+jsonwith a stablecode. See Errors. - Retries: send an
Idempotency-Keywhen you create or rotate a key, upload a file, or create an envelope. See Requests, retries and limits.
Start with the Quickstart.