DEVELOPERS · CHECKID

Create Process

Create a Process inside a Subject with process type, provider, purpose and context.

CONTRACTVersioned API / SDK

AUTHOAuth2 / environment

OUTPUTResponse · result code · evidence

SOURCE-DRIVEN REST CONTRACT

Create Process

Create a verification Process inside a Subject. A Subject may have multiple Processes; each Process belongs to one Subject.

Source contractDigital Trusted Identity Service API And Kafka Specifications · V1.2.260123

POST/v1/create/process

Bearer + OAuth2 Client Credentials3.4 · Creates ProcessSource p.14

Create a verification Process inside a Subject. A Subject may have multiple Processes; each Process belongs to one Subject.

Open in API Explorer ↗

Field	Type	Presence	Description
`subject_id`	String	M	Unique Subject identifier
`provider`	String	O	Identity Service Provider
`process_type`	String	M	Verification process type
`claim_sources`	Object	M/O	Signed claim source for applicable flows
`purpose`	String	M	CREATE · AMEND · ADJUST · AUTHORIZE · ENROLL

REQUEST — redacted sampleNO PRODUCTION SECRET

{
  "subject_id": "<SUBJECT_ID>",
  "provider": "mobile-id",
  "process_type": "LIVE_FACIAL_MATCHING_EKYC",
  "identity_document": {
    "type": "CITIZEN_CARD",
    "value": "<CITIZEN_ID_SAMPLE>"
  },
  "purpose": "CREATE",
  "external_id": "demo-process-001"
}

RESPONSEDOCUMENTED SHAPE

{
  "status": 0,
  "message": "SUCCESSFULLY",
  "dtis_id": "<DTIS_TRANSACTION_ID>",
  "process_id": "<PROCESS_ID>",
  "process_status": "PENDING",
  "provider": "mobile-id"
}

Publication boundaryExamples use explicit placeholders; the website does not send requests to a production environment.

API REFERENCE

Source-backed contract: Create Process

POST · /v1/create/process

Endpoint & purpose

POST /v1/create/process. Create one verification process inside one subject; a subject may contain many processes.

Authentication

Bearer . Do not replace this mechanism with assumptions from legacy documentation.

Publication scope

PARTNER. Source: CheckID API contract V1.2.260123 §2.2.10.

Request shape

{
  "process_type": "FACIAL_IDENTIFICATION",
  "purpose": "CREATE",
  "identity_document": {
    "type": "CITIZEN_CARD",
    "value": "<DOCUMENT_NUMBER>"
  }
}

Response shape

{
  "process_status": "PROCESSING",
  "x-process-id": "<PROCESS_ID>",
  "x-billcode-id": "<BILLCODE_ID>"
}

Failure / recovery

Error semantics must use the raw contract/error catalogue; retry/idempotency/timeout behavior is applied only when a corresponding source defines it.