Create a new request for one or more subjects (users).
This endpoint will:
Documentation Index
Fetch the complete documentation index at: https://humanos.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Optional key used to safely retry the same create/initiate request without duplicating side effects.
"a96d14c5-8e60-4f6b-9d80-5c18c0e4202a"
Pin responses to a specific API version (YYYY-MM-DD). When omitted, defaults to the version stored in your issuer config or today's date.
^\d{4}-\d{2}-\d{2}$"2026-03-03"
Request body containing contacts (subjects), security level, and credentials to generate
Resources can be specified via groupIds, resourcesIds, or inline credentials array.
Array of contact emails or phone numbers
["john.doe@example.com", "+1234567890"]Name to be assigned to the request
"My request"
Security level for the request
CONTACT, ORGANIZATION_KYC, HUMANOS_KYC, HUMANOS_REVALIDATION Ids of existing group resources to be included in the request
["1234567890"]Ids of existing resources to be included in the request
["1234567890"]Inline JSON credentials to be included in the request
What language to use when sending notifications to the user
"ENG"
URL to redirect the subject after completing the request
"https://example.com/callback"
Internal identifier for the request
"order-123"
Base64-encoded P-256 SPKI public key to pre-register for postMessage payload encryption.
"MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE..."
Grants 3 types of access to the request:
READ access to request detail, credentials, and corresponding evidences.
Allows to create Verifiable Presentations (VPs) from mandates associated with this request
Allows to verify Verifiable Presentations (VPs) from mandates associated with this request
By default, the requester DID are automatically appended to this list.
["did:web:google.com", "did:web:google.pt"]List of known document IDs of the users This will force a KYC verification for each user if none of its Humanos identities match the document ID Will make sure the received identity from the KYC verification matches the document ID, and update the user's Humanos identities if needed
[
{
"contact": "john.doe@example.com",
"docId": "1234567890"
}
]Returns information about the new request, subjects, and credentials