> For the complete documentation index, see [llms.txt](https://docs.vcheckglobal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vcheckglobal.com/api-reference/id-verification/id-verification-orders.md). # ID Verification Orders Submit identity verification requests on individuals directly from your platform. **v1 (Production):** `POST /investigation-request` — currently live. **v2 (Future Release):** `POST /idverification/request` — not yet available. ## Submit IDV Request (v2 — Future Release) > \> \*\*Future Release\*\* — This endpoint is not yet available in production. It will be released\ > \> in a future version of the platform. For current integrations, use the v1 endpoint:\ > \> \`POST > \ > When released, this v2 endpoint will accept standard OAuth2 Bearer token authentication\ > and align with the platform's unified request format.\ > \ > \*\*Required fields:\*\* \`investigation\_type\`, \`service\`, \`first\_name\`, \`last\_name\`, \`email\`.\ > \ > \*\*service field:\*\* Pass the product code to specify the verification type —\ > \`IDV\`, \`IDV-FACE\`, or \`IDV-Face-Video-ID-Validation\`.\ > \ > \*\*Rate limit:\*\* 5 requests per second per API key.
```json {"openapi":"3.1.0","info":{"title":"Vcheck Global API","version":"5.4.0"},"tags":[{"name":"ID Verification Orders","description":"Submit identity verification requests on individuals directly from your platform.\n**v1 (Production):** `POST /investigation-request` — currently live.\n**v2 (Future Release):** `POST /idverification/request` — not yet available.\n"}],"servers":[{"url":"https://api-platform.vcheckglobal.net/v2","description":"Vcheck platform (sandbox host issued first; production host after sign-off)"}],"security":[{"bearerAuth":[]}],"components":{"securitySchemes":{"bearerAuth":{"type":"http","scheme":"bearer","bearerFormat":"JWT","description":"Obtain a token via POST https://api-platform.vcheckglobal.net/v2/oauth2/token.\nInclude in all subsequent requests as `Authorization: Bearer `.\nTokens expire after 3,600 seconds - cache and reuse; request a new one only when close to expiry.\n"}}},"paths":{"/idverification/request":{"post":{"tags":["ID Verification Orders"],"operationId":"submitIdvRequest","summary":"Submit IDV Request (v2 — Future Release)","description":"> **Future Release** — This endpoint is not yet available in production. It will be released\n> in a future version of the platform. For current integrations, use the v1 endpoint:\n> `POST https://api-platform.vcheckglobal.net/investigation-request`.\n\nWhen released, this v2 endpoint will accept standard OAuth2 Bearer token authentication\nand align with the platform's unified request format.\n\n**Required fields:** `investigation_type`, `service`, `first_name`, `last_name`, `email`.\n\n**service field:** Pass the product code to specify the verification type —\n`IDV`, `IDV-FACE`, or `IDV-Face-Video-ID-Validation`.\n\n**Rate limit:** 5 requests per second per API key.\n","requestBody":{"required":true,"content":{"application/json":{"schema":{"type":"object","required":["investigation_type","service","first_name","last_name","email"],"properties":{"investigation_type":{"type":"string","enum":["ID_VERIFICATION"],"description":"Type of investigation. Must be ID_VERIFICATION."},"service":{"type":"string","enum":["IDV","IDV-FACE","IDV-Face-Video-ID-Validation"],"description":"Product code specifying the verification type.\nIDV: Standard ID Verification.\nIDV-FACE: ID Verification with Face Match.\nIDV-Face-Video-ID-Validation: ID Verification with Face and Video Validation.\n"},"first_name":{"type":"string","description":"Subject's first name."},"last_name":{"type":"string","description":"Subject's last name."},"email":{"type":"string","format":"email","description":"Subject's email address. Used to deliver the verification link."},"dob":{"type":"string","format":"date","description":"Subject's date of birth (YYYY-MM-DD)."},"phone_number":{"type":"string","description":"Subject's phone number in E.164 format, e.g. +1234567890."},"reference_id":{"type":"string","description":"Your internal reference ID for this subject."},"requisition_number":{"type":"string","description":"Your internal requisition or order number."},"country":{"type":"string","description":"Subject's country of residence. ISO 3166-1 alpha-2 (e.g. US, GB)."}},"additionalProperties":false}}}},"responses":{"201":{"description":"Request submitted successfully.","content":{"application/json":{}}},"400":{"description":"Invalid payload.","content":{"application/json":{}}},"401":{"description":"Missing or invalid Bearer token.","content":{"application/json":{}}},"429":{"description":"Rate limit exceeded (max 5 requests per second).","content":{"application/json":{}}}}}}}} ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.vcheckglobal.com/api-reference/id-verification/id-verification-orders.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.