Skip to content
Dockt Dockt DOCKT

Overview

Dockt Public API 0.1.0

Section titled “Dockt Public API 0.1.0”

Dockt API for workforce and compliance verification workflows. Backend integrations authenticate with an API key or an M2M access token. Start by creating an assessment, upload one or more documents, then poll the returned Document id or receive a signed webhook before reading the decision. Workspace routes resolve ownership from the authenticated principal; never send worker documents directly from an untrusted browser.

Information

  • OpenAPI version: 3.1.0

Operations

Section titled “ Operations ”
GET
/v1/documents
POST
/v1/documents
GET
/v1/documents/{documentId}
DELETE
/v1/documents/{documentId}
GET
/v1/assessments
POST
/v1/assessments
GET
/v1/assessments/{assessmentId}
PATCH
/v1/assessments/{assessmentId}
POST
/v1/assessments/{assessmentId}/documents
DELETE
/v1/assessments/{assessmentId}/documents/{documentId}
GET
/v1/decisions/{decisionId}
GET
/v1/decisions/{decisionId}/outcome
POST
/v1/decisions/{decisionId}/outcome
GET
/v1/webhooks
POST
/v1/webhooks
GET
/v1/webhooks/{webhookId}
DELETE
/v1/webhooks/{webhookId}
PATCH
/v1/webhooks/{webhookId}
POST
/v1/webhooks/{webhookId}/test
GET
/v1/features
PATCH
/v1/features
GET
/v1/social-compliance-packages
GET
/v1/social-compliance-packages/{code}
GET
/v1/auth/login
GET
/v1/auth/signup
GET
/v1/auth/callback
POST
/v1/auth/logout
GET
/v1/auth/me
POST
/v1/auth/scope
GET
/v1/account
PATCH
/v1/account
GET
/v1/account/users
DELETE
/v1/account/users/{userId}
PATCH
/v1/account/users/{userId}
GET
/v1/account/invitations
POST
/v1/account/invitations
POST
/v1/account/invitations/{invitationId}/resend
DELETE
/v1/account/invitations/{invitationId}
GET
/v1/workspace
GET
/v1/workspaces
POST
/v1/workspaces
GET
/v1/workspaces/{workspaceId}
PATCH
/v1/workspaces/{workspaceId}
GET
/v1/account/api-credentials
POST
/v1/account/api-credentials
DELETE
/v1/account/api-credentials/{credentialId}
PATCH
/v1/account/api-credentials/{credentialId}
GET
/v1/api-credentials
POST
/v1/api-credentials
DELETE
/v1/api-credentials/{credentialId}
PATCH
/v1/api-credentials/{credentialId}
POST
Receive a Dockt webhook event WEBHOOK

Authentication

Section titled “ Authentication ”

bearerAuth

Section titled “bearerAuth ”

Send either an opaque Dockt API key or a short-lived M2M access token as Authorization: Bearer <token>. Exchange M2M client credentials at the token_url returned when the credential is created.

Security scheme type: http

Bearer format: Bearer

sessionCookie

Section titled “sessionCookie ”

Browser session established by the /v1/auth login or signup flow. Backend integrations should use API-key or M2M authentication.

Security scheme type: apiKey

Cookie parameter name: dockt_session