API documentation

Signal mapping

Signal mapping is the zero-config path for onboarding a new provider. Decionis infers structure from sample payloads, proposes mappings, validates workflow intent, versions the baseline, and then moves the provider onto a live connector webhook.

Flow

Signal mapping should let an enterprise provider onboard without Decionis staff rewriting payloads by hand.

1. Verify sponsor

Complete public account verification first so the partner receives the onboarding grant and resolved org ID.

2. Create and upload

Open a pilot mapping session, then upload representative CSV, JSON, NDJSON, or JSONL payloads so Decionis can infer fields and propose governance-aware mappings.

3. Dry-run and issue

Confirm required fields, run the dry-run verdict, and then issue the deployment bundle that returns the org ID, API key, connector ID, webhook secret, webhook URL, and policy version.

Zero-config does not mean ungoverned

The zero-config promise is that Decionis infers and proposes the mapping surface automatically. Providers still confirm the inferred mapping, and each material mapping change is versioned so a live baseline can be promoted or rolled back safely.

Recommended first-run sample

Start with a flat event sample when possible. CoolDeal completed onboarding from the API docs alone after switching its first-run sample to `sample_events_flat.jsonl`, which removed avoidable nested-field ambiguity in the mapping step.

curl -O https://decionis.com/examples/sample_events_flat.jsonl

Required fields

The current zero-config builder is strongest when the incoming records can be normalized into event-style operational signals.

Mapping key	Purpose
timestamp_field	When the underlying provider event occurred.
outcome_field	Provider outcome or verdict emitted for the record.
channel_field	Workflow or acquisition channel for the record.
risk_score_field	Confidence or risk expression from the provider, if available.
amount_field	Numeric business value associated with the event, if applicable.
identifier_field	Optional stable case or entity identifier used for audit continuity.

Endpoints

These routes cover sample-driven onboarding from post-verification session creation through dry-run.

POST/v1/public/auth/register/verifyPublic

Verify the sponsor OTP first and capture onboarding.token plus org.id from the response.

POST/v1/public/pilot/signal-mapping/sessionsOnboarding grant or org API key

Create a new mapping session.

curl -X POST https://api.decionis.com/v1/public/pilot/signal-mapping/sessions \
  -H "Authorization: Bearer <onboarding_grant>" \
  -H "Content-Type: application/json" \
  -d '{
    "org_id": "<org_uuid>"
  }'

POST/v1/public/pilot/signal-mapping/sessions/:sessionId/uploadOnboarding grant or org API key

Upload representative sample records to be inferred and mapped.

curl -X POST https://api.decionis.com/v1/public/pilot/signal-mapping/sessions/<session_id>/upload \
  -H "Authorization: Bearer <onboarding_grant>" \
  -H "Content-Type: application/x-ndjson" \
  --data-binary @sample_events_flat.jsonl

PATCH/v1/public/pilot/signal-mapping/sessions/:sessionId/mappingsOnboarding grant or org API key

Confirm or override the inferred mapping keys for the session.

POST/v1/public/pilot/signal-mapping/sessions/:sessionId/dry-runOnboarding grant or org API key

Run the normalized sample through Decionis and return the mapping verdict before production cutover.

POST/v1/public/pilot/signal-mapping/sessions/:sessionId/deployment-bundleOnboarding grant or org API key

Issue the production bundle once the mapping baseline is confirmed. This is the step that returns the org API key.

curl -X POST https://api.decionis.com/v1/public/pilot/signal-mapping/sessions/<session_id>/deployment-bundle \
  -H "Authorization: Bearer <onboarding_grant>" \
  -H "Content-Type: application/json" \
  -d '{
    "provider_key": "partner_webhook",
    "workflow_key": "decision_intake",
    "source_label": "primary_stream"
  }'

Production cutover

Once the deployment bundle is issued, store the returned env values and move live provider traffic onto the Decionis-issued webhook.

# 1. Issue the deployment bundle from the mapping session
POST https://api.decionis.com/v1/public/pilot/signal-mapping/sessions/:sessionId/deployment-bundle

# 2. Store the returned env values in the provider deployment environment
DECIONIS_API_KEY=...
DECIONIS_ORG_ID=...
DECIONIS_CONNECTOR_ID=...
DECIONIS_WEBHOOK_SECRET=...
DECIONIS_WEBHOOK_URL=...
DECIONIS_POLICY_VERSION=...

# 3. Send live events to the Decionis webhook
POST https://api.decionis.com/v1/signals/webhooks/:connectorId

# 4. Optional: configure the outbound WEBHOOK callback destination
POST https://api.decionis.com/v1/orgs/:orgId/integrations/WEBHOOK/connect

Loading…

Decionis API Reference

Base URL: https://api.decionis.com/v1

Quickstart Main site Contact