DKBSignDocs

Get started

Versioning

Path prefixes follow the upstream APIs. There is no Accept-Version header.

Path prefixes

The gateway is a stable public surface. It keeps the version that each product API already uses:

PrefixProduct
/api/v1/...Authentication, profile, MFA, company admin
/api/v4/...Electronic signature
/api/workflows, /api/clients, /api/users, /api/rolesWorkflows and directory
/api/contacts, /api/edm, /api/ai, /api/logs-auditContacts, vault, AI, audit
/api/verificationSignature verification

Compatibility

Additive changes (new optional fields, new endpoints) can appear without a new prefix. Breaking changes get a new path. Pin your integration to the paths documented here and ignore unknown JSON properties.