> ## Documentation Index > Fetch the complete documentation index at: https://docs.kapso.ai/llms.txt > Use this file to discover all available pages before exploring further. # Submit verification documents > Sends 1 to 3 documents to Meta in one request. Each document is a PDF, JPEG, or PNG of 5 MB or less, from an HTTPS `source_url` or a multipart `file`. A submission Meta receives uses one of the portfolio's 3 attempts. `202` means Kapso accepted the request, not that Meta verified the business. Check `state` and `last_error`, then poll the path in `Location`. `Idempotency-Key` is required. After a timeout, retry with the same key and the same documents to get the same submission. The same key with different documents (including a renewed signed URL) returns `409`. Use a new key only for a new attempt, and never while the state is `outcome_unknown`. ## OpenAPI ````yaml /api/platform/v1/openapi-platform.yaml post /whatsapp/portfolios/{portfolio_id}/business_verification/submissions openapi: 3.1.0 info: title: Kapso Platform API version: 0.2.0 description: > Build WhatsApp messaging into your product. Manage customers, connect phone numbers, send broadcasts, and handle conversations. servers: - url: https://api.kapso.ai/platform/v1 description: Production security: - ApiKeyAuth: [] tags: - name: Customers description: Manage customer accounts - name: Setup Links description: WhatsApp onboarding via embedded signup - name: Phone Numbers description: Connect and manage WhatsApp numbers - name: Webhooks description: Subscribe to WhatsApp events - name: Display Names description: Update WhatsApp business display names - name: Broadcasts description: | Send template messages at scale **Alpha**: This API is in alpha and subject to change - name: Conversations description: Manage conversation state - name: Media description: Upload media files for WhatsApp messaging - name: Users description: Manage project team members - name: Inbox Embeds description: Create and manage embeddable inbox access links - name: Webhook Deliveries description: View webhook delivery attempts and their status - name: External API Logs description: View logs of external API calls made by the project - name: Log Search description: Search log events across API, Meta, workflow, and webhook sources - name: Events description: Emit and query project-scoped events - name: Provider Models description: List available AI provider models - name: WhatsApp Flows description: Build interactive WhatsApp Flows for surveys and forms - name: Contacts description: Manage WhatsApp contacts - name: Findings description: Detect recurring problems in conversations and investigate them with AI - name: Notifications description: >- Route project alerts to shared inboxes and Slack channels connected from the Kapso app - name: WhatsApp Funding description: >- Read Kapso funding status and recorded messaging and calling usage, and stop portfolio funding - name: Business Verification description: >- Send business verification documents to Meta for a customer's business portfolio paths: /whatsapp/portfolios/{portfolio_id}/business_verification/submissions: post: tags: - Business Verification summary: Submit verification documents description: > Sends 1 to 3 documents to Meta in one request. Each document is a PDF, JPEG, or PNG of 5 MB or less, from an HTTPS `source_url` or a multipart `file`. A submission Meta receives uses one of the portfolio's 3 attempts. `202` means Kapso accepted the request, not that Meta verified the business. Check `state` and `last_error`, then poll the path in `Location`. `Idempotency-Key` is required. After a timeout, retry with the same key and the same documents to get the same submission. The same key with different documents (including a renewed signed URL) returns `409`. Use a new key only for a new attempt, and never while the state is `outcome_unknown`. operationId: createBusinessVerificationSubmission parameters: - name: portfolio_id in: path required: true description: Meta business portfolio ID of a production number in your project. schema: type: string - name: Idempotency-Key in: header required: true description: 1 to 255 bytes. Non-ASCII characters use more than one byte each. schema: type: string minLength: 1 maxLength: 255 requestBody: required: true content: application/json: schema: type: object required: - documents properties: documents: type: array minItems: 1 maxItems: 3 items: $ref: '#/components/schemas/BusinessVerificationDocumentInput' example: documents: - source_url: https://files.example.com/certificate.pdf roles: - legal_name - source_url: https://files.example.com/bank-statement.pdf roles: - address multipart/form-data: schema: type: object required: - documents properties: documents: type: array description: >- Send fields as `documents[][file]` and `documents[][roles][]`. minItems: 1 maxItems: 3 items: $ref: '#/components/schemas/BusinessVerificationDocumentUpload' responses: '202': description: Submission accepted. Poll it for Meta's decision. headers: Location: description: Path of the submission. schema: type: string content: application/json: schema: type: object required: - data properties: data: $ref: '#/components/schemas/BusinessVerificationSubmission' example: data: id: 5b0f3c9e-7f1a-4c55-9a51-1f9f7d2b8e40 state: pending submitted_at: '2026-10-17T14:05:02Z' decided_at: null documents: - id: 81234 filename: document content_type: application/pdf byte_size: 248113 roles: - legal_name - id: 81235 filename: document content_type: application/pdf byte_size: 391002 roles: - address documents_purged: false documents_purge_after: null rejection_reasons: [] last_error: null '400': description: >- `Idempotency-Key` is missing or too long, or the request doesn't have 1 to 3 documents content: application/json: schema: $ref: '#/components/schemas/BusinessVerificationErrorResponse' example: error: Supply an Idempotency-Key of 1 to 255 bytes code: invalid_idempotency_key '401': $ref: '#/components/responses/UnauthorizedError' '404': $ref: '#/components/responses/BusinessVerificationNotFound' '409': description: > `review_in_progress`, `already_verified`, `attempts_exhausted`, or `ineligible` for the current status, or `idempotency_conflict` when the key was used with different documents content: application/json: schema: $ref: '#/components/schemas/BusinessVerificationErrorResponse' example: error: A verification is already in review with Meta. code: review_in_progress '422': description: >- `document_invalid` for a bad document entry, or `ineligible` when Kapso can't submit for this business content: application/json: schema: $ref: '#/components/schemas/BusinessVerificationErrorResponse' example: error: Document URLs must use HTTPS code: document_invalid components: schemas: BusinessVerificationDocumentInput: type: object additionalProperties: false required: - source_url properties: source_url: type: string format: uri pattern: ^https:// description: >- HTTPS URL that Kapso downloads the file from. Kapso follows up to 5 redirects. roles: $ref: '#/components/schemas/BusinessVerificationDocumentRoles' BusinessVerificationDocumentUpload: type: object additionalProperties: false description: Send exactly one of `file` or `source_url`. properties: file: type: string format: binary source_url: type: string format: uri pattern: ^https:// description: >- HTTPS URL that Kapso downloads the file from. Kapso follows up to 5 redirects. roles: $ref: '#/components/schemas/BusinessVerificationDocumentRoles' oneOf: - required: - file not: required: - source_url - required: - source_url not: required: - file BusinessVerificationSubmission: type: object required: - id - state - submitted_at - decided_at - documents - documents_purged - documents_purge_after - rejection_reasons - last_error properties: id: type: string format: uuid state: type: string description: > `preparing`, `submitting`, `outcome_unknown`, `pending`, `approved`, `failed`, `discarded`, or `revoked`. Treat unknown values as not final. submitted_at: type: - string - 'null' format: date-time decided_at: type: - string - 'null' format: date-time documents: type: array items: $ref: '#/components/schemas/BusinessVerificationDocument' documents_purged: type: boolean description: Kapso deleted the files. Their metadata stays. documents_purge_after: type: - string - 'null' format: date-time rejection_reasons: type: array description: >- Meta's reasons when it rejects the documents. Only on your project's submissions. items: type: object required: - code - requirement - title - summary properties: code: type: string example: LEGAL_NAME_NOT_FOUND_IN_DOCUMENTS requirement: type: - string - 'null' enum: - legal_name - address - null title: type: string summary: type: string last_error: type: - object - 'null' description: >- Why the submission failed before Meta reviewed it, or why Kapso can't confirm that Meta received it. required: - code - message properties: code: type: string message: type: string BusinessVerificationErrorResponse: type: object required: - error - code properties: error: type: string code: type: string description: Stable error code. Don't parse `error`. BusinessVerificationDocumentRoles: type: array description: What the document shows. One document can show both. Optional. items: type: string enum: - legal_name - address BusinessVerificationDocument: type: object required: - id - filename - content_type - byte_size - roles properties: id: type: integer filename: type: string content_type: type: string enum: - application/pdf - image/jpeg - image/png byte_size: type: integer roles: type: array items: type: string enum: - legal_name - address ErrorResponse: type: object required: - error properties: error: type: string responses: UnauthorizedError: description: Missing or invalid API key content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' BusinessVerificationNotFound: description: > No production number in your project belongs to this portfolio, the submission isn't your project's, or business verification isn't enabled for your project content: application/json: schema: $ref: '#/components/schemas/BusinessVerificationErrorResponse' example: error: Verification resource not found code: not_found securitySchemes: ApiKeyAuth: type: apiKey in: header name: X-API-Key ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.