> ## 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. # List Requests > Retrieve a paginated list of your credential requests Each request includes information about the request, credentials, subjects (users) and chosen security level Optional query parameters filter the results: search (matches request or credential name), dateFrom/dateTo (creation-date range), subject (by contact, id, or internalId), internalId, and securityLevel Use pageIndex and pageSize to page through the results ## OpenAPI ````yaml /versions/2026-07-06.yaml get /request openapi: 3.1.0 info: title: Humanos API description: Humanos API version: '1.0' contact: {} servers: [] security: [] tags: - name: humanosApp description: '' paths: /request: get: tags: - Requests summary: List Requests description: >- Retrieve a paginated list of your credential requests Each request includes information about the request, credentials, subjects (users) and chosen security level Optional query parameters filter the results: search (matches request or credential name), dateFrom/dateTo (creation-date range), subject (by contact, id, or internalId), internalId, and securityLevel Use pageIndex and pageSize to page through the results operationId: requests_list parameters: - name: pageIndex required: false in: query description: Zero-based page index. `0` returns the first page. schema: default: 0 example: 0 type: number - name: pageSize required: false in: query description: Number of items per page schema: minimum: 5 maximum: 100 default: 10 example: 10 type: number - name: search required: false in: query description: >- Search query to filter by. Is case-insensitive and does not need to match the entire value. schema: maxLength: 100 example: example type: string - name: dateFrom required: false in: query description: Filter from date (will be converted to start of day in UTC) schema: format: date-time example: '2025-01-01' type: string - name: dateTo required: false in: query description: >- Filter to date (will be converted to end of day in UTC). Requires dateFrom. schema: format: date-time example: '2025-12-31' type: string - name: subject required: false in: query description: Filter by subject (nested object with contact, id, or internalId). schema: example: user@example.com type: string - name: internalId required: false in: query description: >- Identifier to help you identify the request in your own system. We recommend using a unique value. schema: example: internal-12345 type: string - name: securityLevel required: false in: query description: Filter by security level. Can be a single value or array schema: example: - CONTACT - ORGANIZATION_KYC type: array items: type: string enum: - CONTACT - ORGANIZATION_KYC - HUMANOS_KYC - HUMANOS_REVALIDATION - $ref: '#/components/parameters/ApiVersion' responses: '200': description: >- Returns a paginated list of credential requests plus the total number of pages available. content: application/json: schema: $ref: '#/components/schemas/RequestsEntity' '400': description: >- Invalid query parameters — e.g. dateTo without dateFrom, dateTo earlier than dateFrom, search over 100 characters, pageSize outside 5-100, or an invalid securityLevel. content: application/json: schema: type: object properties: statusCode: type: number example: 400 message: type: string example: dateFrom is required when dateTo is provided error: type: string example: Bad Request 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: RequestsEntity: type: object properties: data: description: Array of your credential requests matching the query parameters title: '' type: array items: $ref: '#/components/schemas/RequestEntity' totalPages: type: number description: >- Total number of pages available based on the page size and total count example: 5 required: - data - totalPages RequestEntity: 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 subjects: description: List of subjects (users) associated with this request title: SubjectIssuerEntity type: array items: $ref: '#/components/schemas/RequestSubjectEntity' credentials: description: List of credentials created in this request. title: '' type: array items: $ref: '#/components/schemas/RequestCredentialEntity' 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 required: - id - securityLevel - subjects - credentials - createdAt RequestSubjectEntity: type: object properties: 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 internalId: type: string description: >- Identifier to help you identify the user in your own system. We recommend using a unique value. example: internal-12345 identityStatus: type: string description: Identity status of the subject within the issuer example: HUMANOS enum: - NONE - KYC - HUMANOS 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: - contact - identityStatus RequestCredentialEntity: 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 required: - id - resourceType - status ````