Get started
API & REST webhooks

Connect requests with your existing systems

Use Platform API, HTTP Request and REST Webhooks for scoped, authorized and traceable data exchange.

Start your 30-day free trialBook a demo
No payment required · Trial starts after onboarding
DekaSignAPI & webhooks
POST/api/v1/approval-requests
{
  "workflow_id": "purchase-review",
  "workflow_release_id": "purchase-review@1",
  "external_id": "purchase-0142",
  "form_data": {
    "department": "Operations",
    "amount": 4200000
  }
}
201 CreatedREQ-2026-0142
Event delivery200 OK
approval.completedIllustrative response and webhook delivery
Product illustration · Sample data
Scoped integration-app access
Scopes
Workflow HTTP Request actions
GET / POST
Events with delivery history
Events
BUILT FOR YOUR WORK

The details that keep work moving.

01

Read catalogs and submit requests

Owners configure integration apps, API keys and workflow scopes. Catalogs and schemas help source systems build requests against published versions.

02

Configure HTTP Request visually

Choose GET or POST, an HTTPS endpoint, non-secret headers and a payload with request and form variables. Manage authentication separately through stored credentials.

03

Send events to verified endpoints

REST Webhooks support authentication, signed events and controlled retries. Configure workflow updates or final outcomes for your destination.

04

Trace request origins and progress

Canvas Logging connects Request IDs with requester, time, status and Form UI or API origin. Open details to understand a failing step.

05

Connect customer-owned n8n

Use scoped API keys, workflow webhooks, the integration guide and starter examples. Customers supply their own n8n Cloud or self-hosted instance and destination credentials.

06

Import employees with the HRIS / ERP wizard

Configure the source REST API, map response fields to DekaSign member data, then review the preview before confirming import. Available fields and authentication depend on the source system's API.

DekaSignAPI & webhooks
POST/api/v1/approval-requests
{
  "workflow_id": "purchase-review",
  "workflow_release_id": "purchase-review@1",
  "external_id": "purchase-0142",
  "form_data": {
    "department": "Operations",
    "amount": 4200000
  }
}
201 CreatedREQ-2026-0142
Event delivery200 OK
approval.completedIllustrative response and webhook delivery
Product illustration · Sample data
INSIDE THE WORKSPACE

Design integrations alongside your business process

API Access, Integration Guide, Canvas and delivery logs help teams prepare integrations while keeping request progress visible.

  • Limit API keys to the categories and workflows an application needs.
  • Use schemas and integration examples before submitting real information.
  • Select available variables without placing credentials in form content.
  • Correlate Request IDs and events with the destination application's logs.
FROM START TO FINISH

One clear path through the work.

  1. 01

    Define the data exchange

    Choose data entering through Platform API or updates leaving a workflow.

  2. 02

    Prepare access and destinations

    Scope the integration app and configure required destinations and authentication.

  3. 03

    Test a supported route

    Check schemas, responses and events in the sandbox before requesting applicable activation.

  4. 04

    Monitor Request IDs and deliveries

    Use Canvas Logging and delivery logs to inspect results and failures.

PUT IT INTO PRACTICE

From a team’s need to a clear outcome.

Illustrative scenarios you can adapt to your organization’s policies.

Requests from an internal application

A team wants its operations application to submit approvals through an enabled, supported Platform API route.

  1. The Owner scopes the integration app to relevant categories and workflows.
  2. The developer reads the schema and tests submission with a unique request identity.
  3. The team correlates source-app status with the Request ID in Canvas Logging.

Cross-system submissions remain traceable to their workflow version and source.

Status updates reach an operations system

A team wants its internal system to receive approval outcomes without emailing document copies to every notification recipient.

  1. The administrator prepares the receiving HTTPS endpoint and authentication.
  2. The workflow uses REST Webhooks for selected events.
  3. The team reviews logs and handles repeated deliveries idempotently in the destination system.

The destination receives updates that can be correlated with request history.

Build your process in DekaSign.

Start with the team, forms and documents your work needs.

Start your 30-day free trialBook a demo