ToFF Sign API & Webhook Integration

Programmatic interfaces for initiating document packages, retrieving signing statuses, and receiving real-time webhook events.

1. Authentication

API access requires an authorized Bearer token:

http

Authorization: Bearer <YOUR_DOCUMENSO_API_KEY>

API tokens can be generated under Settings > API & Webhooks in the ToFF Sign portal.

2. Core REST API Endpoints

Create Document from Template

Endpoint: POST /api/v2/templates/{templateId}/generate-document
Content-Type: application/json

bash

curl -X POST https://sign.tomoffinland.org/api/v2/templates/tpl_board_res/generate-document \
  -H "Authorization: Bearer $API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Board Resolution 2026-04",
    "recipients": [
      {
        "name": "Trustee Name",
        "email": "trustee@tomoffinland.org",
        "role": "SIGNER"
      }
    ]
  }'

Get Document Status

Endpoint: GET /api/v2/documents/{documentId}

bash

curl https://sign.tomoffinland.org/api/v2/documents/doc_12345 \
  -H "Authorization: Bearer $API_TOKEN"

3. Webhook Events

Configure webhook endpoints in the administrator panel to receive real-time notifications for automated workflows:

document.created: Fired when a new document is drafted.
document.sent: Fired when invitations are dispatched to recipients.
document.signed: Fired when an individual recipient completes their signing action.
document.completed: Fired when all required parties have completed execution and the certified package is ready.

ToFF Sign API & Webhook Integration ​

1. Authentication ​

2. Core REST API Endpoints ​

Create Document from Template ​