API base
All routes below are rooted at the public API base.
https://api.decionis.com/v1Decionis exposes a governed API surface for signal intake, policy encoding, execution handoff, and Decision Dossier verification. Most integrations start with signal mapping, move onto Decionis-issued webhook ingress, and then consume protocol artifacts.
Use the API base for programmatic requests and the docs surface for reference material.
All routes below are rooted at the public API base.
https://api.decionis.com/v1Share this docs surface with partner engineering teams.
/docs/apiZero-config onboarding starts with a mapping session, then issues a deployment bundle. Live provider traffic moves into Decionis through the Decionis-issued webhook and shared secret returned by that bundle.
These are the primary reference areas for partner integrations.
API key posture, public routes, and webhook trust requirements.
Sample-driven zero-config mapping sessions, required fields, and dry-run validation.
Connector issuance, secret validation, delivery semantics, and retry posture.
Versioned policy bundles and execution dispatch artifact submission.
Org-scoped dossier retrieval, share-safe public verification, and portable artifacts.
Implementation order for teams adopting Decionis for the first time.
| Area | Primary docs path |
|---|---|
| Auth | /docs/auth |
| Signal Mapping | /docs/signal-mapping |
| Webhooks | /docs/webhooks |
| Policy Encoding | /docs/policy-encoding |
| Decision Dossier | /docs/decision-dossier |
| Quickstart | /docs/quickstart |
This is the smallest useful route set for a partner integrating Decionis as a governed decision surface.
/v1/public/pilot/signal-mapping/sessionsPilot accessCreate a sample-driven mapping session before any live traffic is sent into Decionis.
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>"
}'/v1/public/pilot/signal-mapping/sessions/:sessionId/deployment-bundlePilot accessIssue the org ID, API key, connector ID, webhook secret, and webhook URL in one onboarding step.
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"
}'/v1/protocol/policies/bundlesAPI keySubmit a versioned policy bundle when the integration participates in policy authoring.
/v1/public/decision-dossiers/:dossierId/verify?sig=<signature>PublicVerify a Decision Dossier through a share-safe public route without exposing the full org-scoped artifact.
The docs surface should make failure posture explicit so integrators can recover without support.
| Status | Meaning | Expected action |
|---|---|---|
| 400 | Payload shape or required field mismatch | Fix request shape and retry. |
| 401 | Missing or invalid API credentials | Rotate or supply a valid API key. |
| 403 | Caller is outside org or route trust boundary | Use the correct org-scoped credential or public route. |
| 409 | Artifact version or connector state conflict | Resolve the latest state, then resubmit. |
| 422 | Mapping, policy, or dossier input is semantically invalid | Correct the payload content, not just the syntax. |