Get decision
const url = 'https://api.dockt.com/v1/decisions/dec_example';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.dockt.com/v1/decisions/dec_example \ --header 'Authorization: Bearer <token>'Returns the immutable decision for an assessment, including applied policy releases and evaluated requirements.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Unique Dockt decision identifier.
Responses
Section titled “ Responses ”Envelope for a single resource response.
Envelope for a single resource response.
object
Immutable assessment decision with typed policy provenance and evidence requirements for one assessment input version.
object
Unique Dockt decision identifier.
Assessment identifier associated with a decision.
Unique Dockt workspace identifier.
Features version used when the decision was created.
A number greater than or equal to 1
Dockt decision for an assessment based on available worker context and evidence.
Customer-facing traffic-light signal derived from the semantic decision.
A string at least 1 character(s) long
object
A string at least 1 character(s) long
A string at least 1 character(s) long
A string at least 1 character(s) long
A string at least 1 character(s) long
object
A string at least 1 character(s) long
A string at least 1 character(s) long
object
A string at least 1 character(s) long
object
A string at least 1 character(s) long
Exact executable compliance-package release applied to an assessment.
object
A string at least 1 character(s) long
A string at least 1 character(s) long
Policy-neutral evidence requirement and its current assessment status.
object
A string at least 1 character(s) long
Human-readable name shown in Dockt and customer systems.
A string at least 1 character(s) long
Current result of evaluating one evidence requirement.
A string at least 1 character(s) long
ISO 8601 date-time string.
Example
{ "object": "single", "data": { "object": "decision", "id": "dec_example1042", "assessment_id": "ast_example1042", "workspace_id": "wsp_example1042", "features_id": "feat_example1042", "assessment_input_version": 3, "decision": "compliant", "signal": "green", "explanation": "The available evidence satisfies every evaluated requirement for this assessment version.", "findings": [], "facts": [ { "id": "fact_example1042", "code": "person.name", "subject": { "id": "worker_example1042", "type": "worker" }, "value": "Amina Diallo", "resolution": "corroborated", "assurance": "medium", "sources": [ { "kind": "customer_input", "code": "assessment.worker", "document_ids": [], "observed_at": null, "fresh_until": null }, { "kind": "document", "code": "document.holder_name", "document_ids": [ "doc_example1042" ], "observed_at": "2026-08-23T09:30:18Z", "fresh_until": null } ] } ], "documents": [ { "document_id": "doc_example1042", "status": "completed", "document_result": "valid", "finding_ids": [] } ], "recommendation": null, "authority_verification_status": null, "fraud_signal_summary": [], "applied_packages": [ { "code": "social_construction_be_v1", "version": "v1" } ], "requirements": [ { "code": "identity.worker", "label": "Identity document", "reason": "Confirm the identity of the worker being assessed.", "status": "satisfied", "required": true, "source_domain": "social", "package": { "code": "social_construction_be_v1", "version": "v1" }, "accepted_evidence_types": [ "identity_document" ], "supporting_document_ids": [ "doc_example1042" ], "pending_document_ids": [], "review_document_ids": [], "invalid_document_ids": [] } ], "model_version": null, "created_at": "2026-08-23T09:31:00Z" }}The request did not match the expected schema
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "type": "https://docs.dockt.com/errors/invalid-request", "title": "Bad request", "status": 400, "detail": "The request did not match the expected schema.", "instance": "req_example1042"}Problem Details response for HTTP 401. The type URI is the stable machine-readable error code.
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "type": "https://docs.dockt.com/errors/missing-auth", "title": "Unauthorized", "status": 401, "detail": "Send a valid bearer token or browser session.", "instance": "req_example1042"}Problem Details response for HTTP 403. The type URI is the stable machine-readable error code.
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "type": "https://docs.dockt.com/errors/forbidden", "title": "Forbidden", "status": 403, "detail": "The authenticated principal does not have the required permission.", "instance": "req_example1042"}Problem Details response for HTTP 404. The type URI is the stable machine-readable error code.
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "type": "https://docs.dockt.com/errors/not-found", "title": "Not found", "status": 404, "detail": "The requested resource was not found in the authenticated scope.", "instance": "req_example1042"}Problem Details response for HTTP 409. The type URI is the stable machine-readable error code.
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "type": "https://docs.dockt.com/errors/conflict", "title": "Conflict", "status": 409, "detail": "The request conflicts with the current resource state.", "instance": "req_example1042"}Problem Details response for HTTP 422. The type URI is the stable machine-readable error code.
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "type": "https://docs.dockt.com/errors/validation", "title": "Validation failed", "status": 422, "detail": "Correct the invalid fields and send the request again.", "instance": "req_example1042", "errors": { "issues": [ { "path": [ "body", "worker", "nationality" ], "message": "Expected a two-letter country code." } ] }}Problem Details response for HTTP 429. The type URI is the stable machine-readable error code.
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "type": "https://docs.dockt.com/errors/rate-limit", "title": "Too many requests", "status": 429, "detail": "Wait for the Retry-After interval before retrying.", "instance": "req_example1042"}Problem Details response for HTTP 500. The type URI is the stable machine-readable error code.
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "type": "https://docs.dockt.com/errors/internal", "title": "Internal server error", "status": 500, "detail": "Retry the request safely or contact Dockt support with the request ID.", "instance": "req_example1042"}