Create an account
Start here when you need an org workspace, default API keys, or the first SDK/API setup.
https://decionis.com/create-accountLoading…
API documentation
Help and support
Use this page to route Decionis setup and integration questions to the right place. Most support cases are fastest when they include the org ID, request correlation ID, decision ID, dossier URL, SDK version, and the route being called.
Support paths
Choose the path that matches the stage of the integration.
Request integration help
Use the contact path for API-key scope issues, marketplace enablement, onboarding, and deployment support.
https://decionis.com/contact?intent=pilotOpen the workspace
Use the workspace for org-scoped setup, policy encoding, SDK keys, dossiers, validation packs, and protocol views after sign-in.
https://decionis.com/workspaceAPI quickstart
Use the quickstart when the integration is ready to issue a deployment bundle and call the canonical protocol route.
/docs/quickstartSDK guidance
Use the API and decision-evaluation docs when an SDK call needs to be checked against the live protocol route.
/docs/decision-evaluationDossier verification
Use public dossier verification links to share audit-safe evidence without exposing private workspace data.
/docs/decision-dossierBefore contacting support
Include these details so Decionis can diagnose the issue without a long back-and-forth.
Route: https://api.decionis.com/v1/protocol/evaluate-decision
Org ID: <org_uuid>
SDK package and version: decionis==0.1.x | @decionis/sdk@0.1.x | com.decionis:...
Request correlation ID: <x-decionis-request-id or app request id>
Decision ID: <decision_id if returned>
Dossier URL: <dossier_url if returned>
HTTP status and response body: <redact bearer tokens and secrets>
Expected outcome: ALLOW | BLOCK | ESCALATE | REVIEW_REQUIREDDo not send secrets
Never include raw API keys, OAuth client secrets, webhook secrets, private keys, or customer payloads that have not been redacted. Prefixes, route names, status codes, decision IDs, and dossier IDs are usually enough to start diagnosis.
Common issues
These are the first checks for the support cases Decionis sees most often.
404 on a documented API route
Confirm that calls use the production API base and the canonical /v1/protocol/evaluate-decision route for runtime decisions. Older SDK or app code may still call deprecated decision paths.
Policy provisioning returns 403
Policy validation and policy bundle creation require policy read/write scopes. Runtime-only API keys can evaluate decisions but cannot provision policy bundles.
Decision escalates unexpectedly
Check that the org has an active policy bundle for the workflow and that the request includes the expected org ID, workflow key, policy reference, and execution context.
Dossier verification fails
Use the public verification URL returned by Decionis and include the dossier ID plus verification status in the support request.
Reference links
The shortest path to the relevant docs area.
Authentication
API keys, onboarding grants, and route classes.
/docs/authPolicy encoding
Versioned policy bundle submission and execution handoff artifacts.
/docs/policy-encodingValidation packs
Org-level evidence exports, bundle hashes, and regulator-facing downloads.
/docs/validation-packs