Sign API

Quick Start — Sign API

Send your first signature request in two API calls: authenticate, then create a signature request with an inline PDF and a no-account signer.

Prerequisites

• An API username and API key from the Skribble Admin UI
• A PDF document (Base64-encoded)

Step 1 — Authenticate

Code
curl -X POST "https://api.skribble.com/v2/access/login" \
  -H "Content-Type: application/json" \
  -d '{
    "username": "api_your_username",
    "api-key": "your-api-key"
  }'

The response is a plain-text JWT token:

Code
eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...

Save this token — it's valid for ~20 minutes.

Step 2 — Create a signature request

This creates a signature request with an inline Base64 PDF and one SES signer who does not need a Skribble account (no-account signer).

Code
curl -X POST "https://api.skribble.com/v2/signature-requests" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "My first contract",
    "message": "Please sign this document.",
    "quality": "SES",
    "content": "JVBERi0xLjQKMSAwIG9iago8PAovVHlwZSAvQ2F0...",
    "content_type": "application/pdf",
    "signatures": [
      {
        "signer_identity_data": {
          "email_address": "signer@example.com"
        }
      }
    ]
  }'

Response

Code
{
  "id": "abc-123-def",
  "title": "My first contract",
  "status_overall": "OPEN",
  "quality": "SES",
  "signatures": [
    {
      "sid": "sig-456",
      "status_code": "OPEN",
      "signer_identity_data": {
        "email_address": "signer@example.com"
      },
      "signing_url": "https://my.skribble.com/view/abc-123-def/..."
    }
  ]
}

The signer receives an invitation email. Once they sign, the status_overall changes to SIGNED and the signed PDF can be downloaded.

What's next

• Best Practices — callbacks, signer management, signature qualities
• Sign API v2 Reference — full endpoint documentation