Get started
DekaSign for developers

Connect your app.
Keep work moving.

API & REST webhooks

Connect your systems to DekaSign requests, approval workflows and documents. Send data through the REST API and receive process updates through webhooks.

Read the API referenceStart integrating ↓
REST APISandbox & ProductionOutgoing webhooks
Your first API call
GET/api/v1/request-forms
curl "$DEKASIGN_BASE_URL/api/v1/request-forms" \
  -H "Authorization: Bearer $DEKASIGN_API_KEY" \
  -H "X-Dekasign-Environment: sandbox"

Set the variables to your workspace URL and API key. This example reads the permitted catalog.

Integration directions

Send commands. Receive updates.

The REST API and outgoing webhooks work together, each with its own authentication and setup.

Your app → DekaSign

REST API

Read the available catalog and run request or document operations according to your application scopes and supported configurations.

  • An API key for each environment
  • Selected categories, workflows and scopes
  • Idempotency-Key for POST commands
Explore endpoints & payloads →
DekaSign → Your app

Outgoing webhooks

Receive workflow and document events at your endpoint to connect process outcomes with the next step in your systems.

  • A verified HTTPS destination
  • Separate endpoint authentication
  • Delivery history and retries
Explore events & delivery →
Start here

From a designed workflow to a working integration.

Design your forms and templates in DekaSign, then connect your app to the published process.

View the full guide →
  1. 01

    Prepare your process in DekaSign

    Build your form and workflow, then publish the Request Form Template your integration will use.

  2. 02

    Create integration access

    The Owner selects the application, environment, categories, workflows and scopes. Keep the API key on your server.

  3. 03

    Test in Sandbox

    Read the catalog, map your fields and test supported operations. Send an Idempotency-Key with POST commands.

  4. 04

    Connect the outcome

    Set up a webhook endpoint to receive events. Use Production according to your organization's permissions and active paid plan.

Integration essentials

Scoped access. Traceable delivery.

Grant only the access you need and check each operation's outcome before continuing your business process.

Keep credentials on your server

Never place API keys in browser code, public repositories or documents.

Retry with the same identity

Reuse the same Idempotency-Key for the same payload when following up on an uncertain response.

Production follows your permissions

An Owner with an active paid plan manages access. Operation availability follows supported workflows and documents.

Build with DekaSign

Have a process you want to connect?

Read the documentation or talk through your integration needs with our team.

API documentationTalk to our team