docs: sync documentation with document upload schema changes#522
Conversation
Update PASSPORT upload examples to include documentNumber and issuingAuthority fields, which are now required for identity documents after the document upload schema split in #517. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Greptile SummaryThis documentation-only PR syncs the KYC guide with the schema split introduced in #517, which separated document uploads into identity and non-identity types. Both PASSPORT upload curl examples in
Confidence Score: 5/5Safe to merge — documentation-only change that correctly adds two missing required fields to curl examples. Both PASSPORT upload examples now include all required fields ( No files require special attention.
|
| Filename | Overview |
|---|---|
| mintlify/snippets/kyc/kyc-unregulated.mdx | Adds required documentNumber and issuingAuthority fields to both PASSPORT upload examples (individual KYC and KYB beneficial owner), aligning with the IdentityDocumentUploadRequest schema. |
Sequence Diagram
sequenceDiagram
participant Dev as Developer
participant API as Grid API
Dev->>API: POST /customers (customerType, personalInfo)
API-->>Dev: "{ id: "Customer:..." }"
Dev->>API: "POST /documents (multipart/form-data)<br/>documentHolder, documentType=PASSPORT<br/>documentNumber, issuingAuthority, country, file"
API-->>Dev: "{ id: "Document:..." }"
Dev->>API: POST /verifications (customerId)
API-->>Dev: "{ verificationStatus: "IN_PROGRESS" | "RESOLVE_ERRORS" }"
API-->>Dev: Webhook: CUSTOMER.KYC_APPROVED / KYC_REJECTED
Reviews (1): Last reviewed commit: "docs(kyc): add required fields to identi..." | Re-trigger Greptile
Summary
documentNumberandissuingAuthorityfields to identity document upload examples in KYC guideTest plan
IdentityDocumentUploadRequestschema🤖 Generated with Claude Code