Create a verification policy
GENERATED — DO NOT EDIT DIRECTLY. Produced from the canonical OpenAPI specification by
developer-docs/tools/generate-reference.mjs. Edits are overwritten on the next run.
POST
/management/verification-policiesScope: verification-policies.manage. Names the credential configurations a presentation must satisfy. Activated on creation unless activate is false - a Draft policy cannot be used to start a verification. Authenticate with Authorization: ApiKey {key}. Every response carries x-ms-request-id, X-Correlation-Id and X-Request-Id; quote the request id in any support request. Returns 201 on success.
| Operation ID | VerificationPolicies_Create |
| Plane | Management |
| Versioning | ?api-version=2026-08-30 |
| Authentication | Authorization: ApiKey {key} |
| Required scope | verification-policies.manage |
| Concurrency | Not applicable |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
api-version |
string |
Yes | Management API version. Supported: 2026-08-30. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
x-ms-client-request-id |
string |
No | Optional caller-supplied correlation value, echoed back on the response and recorded in diagnostics. It never influences authentication, tenant or environment selection, resource lookup or idempotency. |
Request body
Type: CreatePublicVerificationPolicyRequest
| Field | Type | Required | Description |
|---|---|---|---|
activate |
boolean |
No | |
credentialConfigurations |
array of string |
Yes | |
description |
string, nullable |
No | |
displayName |
string |
Yes | |
failClosedOnStatusFailure |
boolean |
No | |
maximumCredentialAgeSeconds |
integer, nullable |
No | |
organisationReference |
string |
Yes | |
policyIdentifier |
string |
Yes | |
requireActiveCredentialStatus |
boolean |
No | |
requireHolderBinding |
boolean |
No |
Responses
| Status | Body | Meaning |
|---|---|---|
201 |
ManagementResourceOfPublicVerificationPolicyResponse |
Created. |
400 |
ErrorEnvelope |
The request was not valid. See error model. |
401 |
ErrorEnvelope |
Authentication failed — the API key is missing, malformed, revoked or expired. |
403 |
ErrorEnvelope |
Authenticated, but the key does not carry the required scope. |
404 |
ErrorEnvelope |
Not visible to this caller. A resource in another tenant or environment reports as not found. |
409 |
ErrorEnvelope |
The request conflicts with the resource state, or an idempotency key was reused with a different payload. |
429 |
ErrorEnvelope |
Throttled. See rate limits. |
Response headers: x-ms-request-id
Example
curl -X POST "https://api.example.diligence.id/management/verification-policies?api-version=2026-08-30" \
-H "Authorization: ApiKey YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ }'