> ## Documentation Index > Fetch the complete documentation index at: https://docs.humanos.tech/llms.txt > Use this file to discover all available pages before exploring further. # Get Detail > Retrieve detailed information about a specific credential request Just like the list requests endpoint, this endpoint includes information about the request, credentials, subjects (users) and chosen security level However, this endpoint includes the full W3C Verifiable Credential data for each credential, and the latest status of all grantor decisions ## OpenAPI ````yaml /versions/2026-07-06.yaml get /request/{requestId} openapi: 3.1.0 info: title: Humanos API description: Humanos API version: '1.0' contact: {} servers: [] security: [] tags: - name: humanosApp description: '' paths: /request/{requestId}: get: tags: - Requests summary: Get Detail description: >- Retrieve detailed information about a specific credential request Just like the list requests endpoint, this endpoint includes information about the request, credentials, subjects (users) and chosen security level However, this endpoint includes the full W3C Verifiable Credential data for each credential, and the latest status of all grantor decisions operationId: requests_detail parameters: - name: requestId required: true in: path description: >- Unique identifier of the credential request. Must be a valid MongoDB ObjectId. schema: example: 507f1f77bcf86cd799439011 type: string - $ref: '#/components/parameters/ApiVersion' responses: '200': description: >- Returns complete information including W3C Verifiable Credentials, subjects, and issuer details. content: application/json: schema: $ref: '#/components/schemas/RequestDetailEntity' '400': description: The requestId path parameter is not a valid MongoDB ObjectId. content: application/json: schema: type: object properties: statusCode: type: number example: 400 message: type: string example: requestId is not a valid MongoDB id error: type: string example: Bad Request '404': description: >- Request not found (unknown id, or the request belongs to another issuer). Canceled requests are still returned. content: application/json: schema: type: object properties: statusCode: type: number example: 404 message: type: string example: Request not found error: type: string example: Not Found components: parameters: ApiVersion: name: API-Version in: header required: false schema: type: string pattern: ^\d{4}-\d{2}-\d{2}$ example: '2026-07-06' description: >- Pin request, response, and webhook shapes to a specific dated API version (YYYY-MM-DD). Omit to use the version pinned to your API key (set when the key is created; new keys default to the latest version). New integrations should target the latest version. schemas: RequestDetailEntity: type: object properties: id: type: string description: Unique identifier for the request example: 507f1f77bcf86cd799439011 name: type: string description: Name of the credential request example: Employee Onboarding Request nullable: true securityLevel: type: string description: Identity level required for all subjects in this request example: CONTACT enum: - CONTACT - ORGANIZATION_KYC - HUMANOS_KYC - HUMANOS_REVALIDATION language: type: string description: >- Language used in the OTP and displayed in the subject link. One of ENG, PRT, SPA, or FRA. example: ENG nullable: true redirectUrl: type: string description: URL to redirect the subject after completing the request example: https://example.com/callback nullable: true internalId: type: string description: Internal identifier for the request example: order-123 nullable: true createdAt: type: string description: Date and time of the request creation example: '2025-01-15T10:30:00Z' format: date-time canceledAt: type: string description: Date and time the request was canceled, null if active example: '2025-01-16T08:00:00Z' format: date-time nullable: true subjects: description: List of subjects with organization data type: array items: $ref: '#/components/schemas/RequestDetailSubjectEntity' credentials: description: List of credentials created in this request type: array items: $ref: '#/components/schemas/CredentialEntity' required: - id - securityLevel - createdAt - subjects - credentials RequestDetailSubjectEntity: type: object properties: contacts: description: List of verified contacts associated with the user title: SubjectIssuerEntity type: array items: $ref: '#/components/schemas/ContactEntity' identityStatus: type: string description: Identity status of the subject within the issuer example: HUMANOS enum: - NONE - KYC - HUMANOS internalId: type: string description: >- Identifier to help you identify the user in your own system. We recommend using a unique value. example: internal-12345 organization: description: >- Contacts collected by your organization for this user. Identity data is never exposed through this API. allOf: - $ref: '#/components/schemas/OrganizationDataEntity' createdAt: type: string description: Date the subject was first registered format: date-time example: '2025-01-15T09:30:00.000Z' id: type: string description: Subject DID example: did:web:humanos.tech:user:73ebefdd-a549-4873-aad9-def80c40c8c8 contact: type: string description: Verified contact value (email or phone) example: user@example.com kyc: type: string description: >- Status of the identity verification process: PENDING, APPROVED, or REJECTED. If undefined, no identity verification was initiated in this request example: PENDING secondaryContact: type: string description: >- Secondary contact (email or phone) used for two-factor authentication in this request. Present when the request was created with a secondary contact for 2FA. example: '+351912345678' nullable: true required: - contacts - identityStatus - organization - createdAt - contact CredentialEntity: type: object properties: id: type: string description: URN of the credential. example: urn:via:credential:550e8400-e29b-41d4-a716-446655440000 name: type: string description: Human-readable name of the credential; null when unset. example: Credential Name description: type: string description: Free-text description of the credential; null when unset. example: Document to be requested on onboarding internalId: type: string description: >- Identifier to help you identify the credential in your own system. We recommend using a unique value. example: internal-12345 resourceType: type: string description: >- The type of resource for this credential (e.g., DOCUMENT, CONSENT, FORM) example: DOCUMENT status: type: string description: The status of the credential example: DRAFT enum: - DRAFT - ACTIVE - REJECTED - CANCELED - REVOKED - EXPIRED tags: description: Free-form labels attached to the credential. example: - onboarding - kyc type: array items: type: string w3cCredential: type: object description: >- The W3C Verifiable Credential following the VIA protocol specification. While the credential is in DRAFT status, this object is in building mode: evidences, proofs, and other fields may still be attached or modified as grantors review and decide. The `proofs` array will be empty at this stage. Once all grantors have accepted (or the request window expires), the status transitions out of DRAFT and cryptographic signature proofs are attached. At that point the credential is fully sealed and can be passed for verification as defined by the VIA protocol. example: '@context': - https://www.w3.org/ns/credentials/v2 - https://via.humanos.dev/ns/v1 id: urn:via:credential:550e8400-e29b-41d4-a716-446655440000 type: - VerifiableCredential - VIAMandate issuer: did:web:humanos.tech validFrom: '2025-01-01T00:00:00Z' validUntil: null credentialSubject: id: did:web:humanos.tech:org:550e8400-e29b-41d4-a716-446655440000 mandate: grantor: did:web:humanos.tech:user:7c9e6679-7425-40de-944b-e07fc1f90ae7 scope: humanos.credential.request context: authorizedDIDs: - >- did:web:humanos.tech:org:550e8400-e29b-41d4-a716-446655440000 - >- did:web:humanos.tech:user:7c9e6679-7425-40de-944b-e07fc1f90ae7 evidences: - id: urn:via:evidence:9b2e4f1a-3c7d-4e8a-bf12-2a6c5d8e0f34 digestSRI: sha256-abc123 location: >- https://api.humanos.dev/credential/evidence/urn:via:evidence:9b2e4f1a-3c7d-4e8a-bf12-2a6c5d8e0f34 proofs: - type: DataIntegrityProof cryptosuite: eddsa-jcs-2022 verificationMethod: did:web:example.com#key-1 created: '2026-05-02T10:15:30.000Z' proofPurpose: assertionMethod proofValue: z2pcVdSdoMTrkYP9rVdz... action: ISSUE actionProof: sha256-9b2e4f1a3c7d4e8abf122a6c5d8e0f34abc123def456... - type: DataIntegrityProof cryptosuite: eddsa-jcs-2022 verificationMethod: >- did:web:humanos.tech:user:7c9e6679-7425-40de-944b-e07fc1f90ae7#key-1 created: '2026-05-02T10:15:30.000Z' proofPurpose: assertionMethod proofValue: z2pcVdSdoMTrkTCXzp... action: ACCEPT actionProof: sha256-9b2e4f1a3c7d4e8abf122a6c5d8e0f34abc123def457... - type: DataIntegrityProof cryptosuite: eddsa-jcs-2022 verificationMethod: did:web:humanos.tech#key-1 created: '2026-05-02T10:15:30.000Z' proofPurpose: assertionMethod proofValue: z2pcVdSdoMTrkTRrXdz... action: STAMP actionProof: sha256-9b2e4f1a3c7d4e8abf122a6c5d8e0f34abc123def458... decisions: description: >- Whether each grantor accepted or rejected the credential and information about the grantor contact. The `id` field carries the grantor's DID. Always an array (empty when there are no decisions yet). example: - id: did:web:humanos.tech:user:7c9e6679-7425-40de-944b-e07fc1f90ae7 contact: grantor@example.com accepted: true decidedAt: '2025-06-01T12:00:00.000Z' type: array items: type: array required: - id - resourceType - status - w3cCredential - decisions ContactEntity: type: object properties: id: type: string description: Contact DID example: did:web:humanos.tech:user:73ebefdd-a549-4873-aad9-def80c40c8c8 contact: type: string description: Verified contact value (email or phone) example: user@example.com required: - id - contact OrganizationDataEntity: type: object properties: contacts: description: Raw contact strings (email/phone) submitted by the organization example: - user@example.com - '+351912345678' type: array items: type: string required: - contacts ````