REST API
Document and dossier operations exposed through HTTP contracts.
Integrations
Integration that runs both ways.
Read documents, approvals and decisions out of DOK Genius through a versioned API and webhooks. And let DOK Genius call into your business system when a process reaches its conclusion — idempotent, waiting for the answer, and keeping a record of what was sent.
APIWebhooksOutboxStorageCRMERPBIEmail
Connection points built for IT teams.
Nothing connects on its own. Every connection is configured, tested against the real destination and switched on by you — and it stays that way.
Webhooks
Events to sync decisions and changes with external systems.
Notifications and delivery, configured for your flow.
File storage
Per-tenant storage with a configurable strategy.
CRM
Leads, commercial requests and follow-up.
ERP
Integration with administrative and financial processes.
BI / Analytics
Operational data prepared for analysis and reporting.
Internal automation
Events and jobs for reliable internal flows.
Operations in your system
The other direction: DOK Genius calls you.
A webhook tells your system something happened. This is not that. At the point a process reaches its conclusion, DOK Genius invokes the business operation in the system that owns it — issue the policy, open the claim, register the order — and waits for the answer before closing the case.
It never runs twice
Every execution carries a unique idempotency key. A retry returns the previous result instead of repeating the operation, and a destination that cannot tolerate repetition is never retried blindly — the failure is marked unsafe to repeat and raised to a person.
It waits for the real answer
If the operation takes time, the case waits on a signed callback with a deadline rather than assuming success. A duplicate callback is recognised as such; one that contradicts the first is told apart from it.
Every value knows where it came from
Alongside what was sent, DOK Genius records which document, which field or which AI reading produced each value. Months later, "why did we send this number" has a documented answer rather than a guess.
Credentials stay out of the record
Secrets are encrypted at rest and redacted from every request and response log. The destination address is re-validated before each call, including after redirects, so an integration cannot be turned into a route into your infrastructure.
You prove it before you switch it on
Preview the payload, validate the configuration and fire a real test call at the destination — without touching a single production case. Nothing goes live until it has answered you once.
It picks up where it stopped
Processing is a plan of ordered steps, each with its own outcome. When one fails, the dossier shows which, and repeating resumes there — the reading a person already validated is not run again, and a call whose effect is confirmed is never repeated without explicit confirmation.
Architecture
Designed for IT teams.
Enterprise integration demands clear contracts, reliable events and authentication.
Versioned API
Stable contracts for critical operations.
Business events
Dossiers, documents and approvals as integrable events.
Outbox for reliable delivery
A foundation for consistent async processing.
Retry & monitoring
Built for observability and controlled recovery.
Authenticated access
Technical access protected by credentials and permissions.
Get started
Let's talk about your integration.
Describe your existing systems and we'll validate the right technical approach.