# Sig.Surf REST API

Source: https://sig.surf/integrations/rest-api (Markdown version of the page)

A JSON API for creating signatures and managing employees, with an OpenAPI description at a stable URL.

> Signatures made through this interface are for Gmail and Google Workspace.

## What you can do

- `POST /api/v1/signatures` with no credentials takes a template id or a signature document plus field values, and returns rendered HTML, plain text, warnings and a claim link. Someone signs in later and claims it; unclaimed signatures expire after 30 days.
- With an API key, list and update employees for your organization.
- List the template catalogue.

## Conventions

- JSON in and out. Errors look like `{ "error": { "code", "message" } }` with the matching HTTP status.
- API keys start with `ssk_`, act for one organization, and are sent as a bearer token. Only a hash of each key is stored.
- Request bodies are limited to 64 KiB. Anonymous callers are rate limited, and you get `429` with a `Retry-After` header.
- The OpenAPI 3.1 document is at `/api/v1/openapi.json`.

For assistants that speak MCP, see the [MCP server](https://sig.surf/integrations/mcp-server).
