Skip to main content
Suresign gives developers three ways to connect their own tools to a workspace: an API to read documents and download PDFs, signed webhooks that tell your app when something happens, and (coming soon) an MCP server so AI assistants can work with your documents. This page explains what each one is for and where to start.
API keys, the API and webhooks are available on the Pro and Business plans. See Plans & Billing.

​
What you can build

​
How it fits together

1

Create an API key

An admin creates a key in Settings > Developers. It starts with dtd_ and is shown once, so store it somewhere safe. See Authentication.
2

Read documents with the API

Send the key as Authorization: Bearer dtd_... to list documents and download PDFs from https://suresign.si/api/v1. See REST API.
3

Listen for events with webhooks

Add a webhook endpoint so your app hears about signing events as they happen, instead of checking again and again. See Webhooks.

​
Next steps

Authentication

Create and protect your API keys.

API Introduction

What the API can do today.

Webhooks

Receive and verify signing events.

MCP

Connect AI assistants to Suresign.