docs(kyc): align EDD sandbox example with OpenAPI schema - #755
Merged
Conversation
The sandbox-verification.mdx example referenced a non-existent
`POST /customers/edd` endpoint and used an invalid `PERSONAL_SPEND`
enum value. Updated to:
- Use `PATCH /customers/{customerId}` (the actual endpoint for EDD)
- Replace `PERSONAL_SPEND` with valid `P2P_TRANSFERS` from PurposeOfAccount enum
- Add required `customerType: INDIVIDUAL` to the PATCH request body
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Greptile SummaryThe PR corrects the sandbox EDD example to use the schema-defined customer PATCH endpoint, required customer type discriminator, and valid purpose-of-account enum.
Confidence Score: 5/5The PR appears safe to merge with no actionable defects identified. The documented endpoint, required customer type discriminator, EDD field placement, and revised enum values all align with the current OpenAPI definitions.
|
| Filename | Overview |
|---|---|
| mintlify/snippets/sandbox-verification.mdx | The revised EDD curl example matches the customer PATCH route and individual-customer update schema. |
Reviews (1): Last reviewed commit: "docs(kyc): align EDD sandbox example wit..." | Re-trigger Greptile
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
jklein24
approved these changes
Jul 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PATCH /customers/{customerId}instead of non-existentPOST /customers/edd)PERSONAL_SPENDenum value with validP2P_TRANSFERSfrom PurposeOfAccount schemacustomerType: INDIVIDUALto PATCH request bodyThis sync addresses documentation drift from the Grid Programmatic KYC API (#726) changes.
Test plan
P2P_TRANSFERSis a valid PurposeOfAccount enum value inopenapi/components/schemas/customers/PurposeOfAccount.yamlPATCH /customers/{customerId}perCustomerEdd.yamldescription andIndividualCustomerUpdateRequest.yamlschemamake lint- no new errors🤖 Generated with Claude Code