Reject Identity Document

POST

api

crew

identity-documents

{document_id}

reject

Reject Identity Document

curl --request POST \
  --url https://api.example.com/api/v1/crew/identity-documents/{document_id}/reject \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "reason": "<string>"
}
'

{
  "targetType": "<string>",
  "targetId": "<string>",
  "rejectionReason": "<string>",
  "reviewedAt": "2023-11-07T05:31:56Z"
}

Authorizations

Authorization

string

header

required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

document_id

string<uuid>

required

Body

application/json

Body for the reject endpoint.

reason

string

required

Response

Successful Response

API response shape (camelCase). Used both as the per-item entry in a profile summary and embedded as the verification field on a credential response.

targetType

string

required

targetId

string

required

status

enum<string>

required

Per-item review state.

Available options:

not_submitted,

pending,

verified,

rejected

rejectionReason

string | null

reviewedAt

string<date-time> | null

List Crew RosterPaginated crew roster, filterable by verification + assignment status. Staff-only; entitlement enforced at the router. Verification state is attached inline (batched, no N+1); a user with no cache row reads as `incomplete`. Both filters are org-scoped SQL subqueries (no IDOR/N+1).

Reject Identity Document

curl --request POST \
  --url https://api.example.com/api/v1/crew/identity-documents/{document_id}/reject \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "reason": "<string>"
}
'

{
  "targetType": "<string>",
  "targetId": "<string>",
  "rejectionReason": "<string>",
  "reviewedAt": "2023-11-07T05:31:56Z"
}