Rewrite maxSpendPerTransaction descriptions in plain language - #956
Rewrite maxSpendPerTransaction descriptions in plain language#956AaryamanBhute wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
✱ Stainless preview builds for gridThis PR will update the cli go kotlin openapi php python ruby typescript Edit this comment to update them. They will appear in their respective SDK's changelogs. ✅ grid-typescript studio · code · diff
✅ grid-openapi studio · code · diff
✅ grid-ruby studio · code · diff
✅ grid-kotlin studio · code · diff
✅ grid-go studio · code · diff
✅ grid-python studio · code · diff
✅ grid-php studio · code · diff
✅ grid-cli studio · code · diff
This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push. |
|
📌 Bolt Status 2026-09-12 01:47:00 UTC — ⚡ Agent |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
@bolt fix merge conflicts |
…Transaction Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Q2vqFy3cS8cukWkLdMwZTP
0a56042 to
3a6f822
Compare
|
⚡ Revision log — updated in place, latest first. Revision 1
|

Summary
Rewrites every
maxSpendPerTransactiondescription in plain language. The old textread like an internal spec — "card-specific cap", "the effective limit", "Grid enforces
the lower of the two values without replacing this configured value". The new text says
what the field does in the second-person voice the rest of the docs use, and spells out
"smallest unit of the currency" with a concrete example (cents for USD) so a reader does
not have to infer it.
No schema constraints, types, examples, or field names changed — description strings only.
Changes: 7 source files (+ 2 regenerated bundles)
openapi/components/schemas/cards/Card.yaml— the field on the card resourceopenapi/components/schemas/cards/CardCreateRequest.yaml—POST /cardsopenapi/components/schemas/cards/CardUpdateRequest.yaml—PATCH /cards/{id}openapi/components/schemas/config/CardConfig.yaml— the platform-wide capopenapi/paths/cards/cards_{id}.yaml— the bullet in thePATCHoperation descriptionmintlify/snippets/cards/issuing-cards.mdx— the field table rowmintlify/snippets/cards/freezing-and-closing.mdx— the per-transaction limit sectionopenapi.yaml,mintlify/openapi.yaml— regenerated bymake buildFacts preserved in every rewrite: the value is in the currency's smallest unit;
null/omitted means no limit; the lower of the card and platform values applies; the
supportsSpendLimitscapability gate; and that it cannot be sent alongsidestate: CLOSED. The "a transaction for exactly the effective limit is allowed" sentencewas dropped in a follow-up commit — it was the fiddliest part of the old text, and cutting
it removes the ambiguity rather than wording around it.
The sibling
maxSpendPerDayandmaxTransactionsPerDaydescriptions were left alone —the request named
maxSpendPerTransaction. They can get the same treatment in afollow-up if you want the whole limits family to read consistently.
Rebased onto main
mainpicked up #934, which renamesfundingSources(array) →fundingSource(singlestring) and rewrites prose in the same description blocks this PR touches — so the two
conflicted. Resolved by keeping
main's singularfundingSourcewording everywhere andre-applying only the
maxSpendPerTransactionrewrites on top. The conflicted bundles wereregenerated with
make buildrather than hand-merged.Test plan
make build— bundles cleanly, and a second run after the rebase produces zero drift,so the committed bundles match the sources
make lint— "Your API description is valid", 2 warnings / 14 ignored, identical tothe pre-change baseline on
main(verified by stashing and re-running)origin/mainoncedescriptionkeys are stripped, so nothing but prose movedfundingSourcescrept back in during the rebase;Detect breaking changespassesOriginal PR: #950