1. Create session
Open a pilot mapping session for the org or cycle you want to validate.
Loading…
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, 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.
2. Upload sample
Upload representative CSV, JSON, 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, and webhook URL.
Zero-config does not mean zero validation
The zero-config promise is that Decionis infers and proposes the mapping surface automatically. Providers still need to confirm the inferred mapping before Decionis issues live webhook credentials.
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. |
Endpoints
These routes cover sample-driven onboarding from session creation through dry-run.
POST
/v1/public/pilot/signal-mapping/sessionsPilot accessCreate a new mapping session.
curl -X POST https://api.decionis.com/v1/public/pilot/signal-mapping/sessions \
-H "Authorization: Bearer sk_org_xxx" \
-H "Content-Type: application/json" \
-d '{
"org_id": "<org_uuid>"
}'POST
/v1/public/pilot/signal-mapping/sessions/:sessionId/uploadPilot accessUpload representative sample records to be inferred and mapped.
PATCH
/v1/public/pilot/signal-mapping/sessions/:sessionId/mappingsPilot accessConfirm or override the inferred mapping keys for the session.
POST
/v1/public/pilot/signal-mapping/sessions/:sessionId/dry-runPilot accessRun the normalized sample through Decionis and return the mapping verdict before production cutover.
POST
/v1/public/pilot/signal-mapping/sessions/:sessionId/deployment-bundlePilot accessIssue the production bundle once the mapping baseline is confirmed.
curl -X POST https://api.decionis.com/v1/public/pilot/signal-mapping/sessions/<session_id>/deployment-bundle \
-H "Authorization: Bearer sk_org_xxx" \
-H "Content-Type: application/json" \
-d '{
"provider_key": "enilo_ai",
"workflow_key": "eligibility_assessment",
"source_label": "enilo_primary"
}'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=...
# 3. Send live events to the Decionis webhook
POST https://api.decionis.com/v1/signals/webhooks/:connectorId