docs(cards): document maxSpendPerTransaction field - #855
Conversation
Document the per-transaction spending limit field added to cards in commit 3fb4289. The OpenAPI spec and API reference pages already include the field; this syncs the guides. Changes: - issuing-cards.mdx: add maxSpendPerTransaction to request table and example curl - freezing-and-closing.mdx: mention maxSpendPerTransaction in intro, add "Updating the per-transaction limit" section with curl example Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Greptile SummaryThis PR adds
Confidence Score: 4/5The PR should be corrected before merging because the new update guide directs developers through a challenge flow that the endpoint does not implement. The create-card documentation matches the schema, but the update section requires a prior 202 response and signing headers even though the current PATCH contract uses platform authentication and returns 200 directly. Files Needing Attention: mintlify/snippets/cards/freezing-and-closing.mdx
|
| Filename | Overview |
|---|---|
| mintlify/snippets/cards/freezing-and-closing.mdx | Adds accurate limit-value semantics but incorrectly documents the update as a signed-retry operation. |
| mintlify/snippets/cards/issuing-cards.mdx | Adds a valid creation example and field description consistent with the create-card OpenAPI schema. |
Prompt To Fix All With AI
### Issue 1
mintlify/snippets/cards/freezing-and-closing.mdx:135-136
**Signed-retry flow contradicts PATCH contract**
When a developer follows this new limit-update example, the guide requires a prior `202` challenge plus `Grid-Wallet-Signature` and `Request-Id`, while the current `PATCH /cards/{id}` contract uses platform credentials and returns `200` directly. The developer therefore waits for a challenge and request ID that the endpoint never returns, preventing completion of the documented update flow.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Reviews (1): Last reviewed commit: "docs(cards): document maxSpendPerTransac..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| curl -X PATCH "$GRID_BASE_URL/cards/Card:019542f5-b3e7-1d02-0000-000000000010" \ | ||
| -u "$GRID_CLIENT_ID:$GRID_CLIENT_SECRET" \ |
There was a problem hiding this comment.
When a developer follows this new limit-update example, the guide requires a prior 202 challenge plus Grid-Wallet-Signature and Request-Id, while the current PATCH /cards/{id} contract uses platform credentials and returns 200 directly. The developer therefore waits for a challenge and request ID that the endpoint never returns, preventing completion of the documented update flow.
Knowledge Base Used: Mintlify Documentation Site
Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/snippets/cards/freezing-and-closing.mdx
Line: 135-136
Comment:
**Signed-retry flow contradicts PATCH contract**
When a developer follows this new limit-update example, the guide requires a prior `202` challenge plus `Grid-Wallet-Signature` and `Request-Id`, while the current `PATCH /cards/{id}` contract uses platform credentials and returns `200` directly. The developer therefore waits for a challenge and request ID that the endpoint never returns, preventing completion of the documented update flow.
**Knowledge Base Used:** [Mintlify Documentation Site](https://app.greptile.com/lightspark/-/custom-context/knowledge-base/lightsparkdev/grid-api/-/docs/mintlify-docs-site.md)
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Summary
Syncs card documentation with the
maxSpendPerTransactionfield added in #818 (commit 3fb4289).maxSpendPerTransactionto the request table and example curlThe OpenAPI spec and API reference pages already include the field; this brings the guides in line.
Test plan
make lintpasses🤖 Generated with Claude Code