[pengying]

Adds changelog entries for Grid API changes that shipped between 2026-10-26 and 2026-11-02. They go at the top of the existing October 2026 block, following the file's one-<Update>-per-month convention. Nothing customer-facing shipped in November yet. The only November merge, #1246, is behind a feature gate.

Slack #shipped had no posts in this window. Each entry below was cross-checked between the grid-api spec PR and the webdev backend PR, plus Jira where a ticket exists. Field names come from the current openapi/ sources.

Entries

Entry	Sources
Card velocity limits move to /card-velocity-limits (breaking: removes maxSpendPerTransaction, maxSpendPerDay, maxTransactionsPerDay and three capability flags)	#1225; webdev #39021, #39253, #39019
Read card disputes (GET /transactions/{transactionId}/disputes, GET /card-disputes/{disputeId})	#1206 (spec, 2026-10-23); webdev #38402 (backend, 2026-10-26)
Machine-readable refusal reasons (details.refusalReason)	#1232; webdev #39080
Exchange rates report corridor availability (isAvailable)	#1244; webdev #39342
SWIFT railDetails with uetr	#1238; webdev #39168, #39130
RESIDENCE_PERMIT identity document	#1249; webdev #39403; AT-7014, AT-7015
Create an individual customer from a KYC share token (POST /customers/share)	#1137 (spec, 2026-10-21); AT-6997 epic resolved 2026-10-29; webdev #39205, #39222, #39224, #39230, #39245, #39344
USDC and USDT rule-based accounts + rule-based accounts guide	#1243; webdev #39441, #39316
ACH pull guide	#1254 (docs only)

Needs confirmation

• POST /customers/share: the spec PR merged 2026-10-21, before this window. I included it because the Jira epic and the backend fixes landed in the window and the changelog has no entry for it. Remove it if it shipped earlier or is limited to specific partners.
• Card disputes: the spec merged 2026-10-23, and the backend read endpoints merged 2026-10-26. Please confirm the endpoints are live in production.
• USDC and USDT rule-based accounts: the spec says these are "enabled per platform", and the backend checks GRID_RULE_BASED_CRYPTO_ACCOUNTS_ENABLED. Please confirm they are offered generally and not limited to a pilot. If they are limited, drop that paragraph and keep the guide link.
• Card velocity limits: this is a breaking removal of fields. Please confirm the backend migration (webdev #39253, #39021) is deployed to production, and decide whether this also needs a direct customer notice.
• ACH pull guide: source is a docs PR only. Please confirm ACH pull is generally available.

Deliberately excluded

• Pay a BOLT11 Lightning invoice through quotes (Grid: pay a BOLT11 Lightning invoice through quotes, agents included #1228): the webdev backend (#39059) is behind a gate.
• Agent single-use purchase cards and card reveal (Agents: single-use purchase cards and card reveal #1237), agent card hand-over (Add agent card hand-over #1239), recurring purchase cards (feat(agents): recurring purchase cards locked to one merchant #1246): these are behind GRID_AGENT_PURCHASE_CARDS_ENABLED and related gates.
• Real-time card authorization (feat(cards): real-time card authorization endpoint #1212, feat(cards): send card authorization requests to webhookEndpoint, configured through platform config #1247): I found no matching webdev backend change in the window. This needs confirmation before it goes in the changelog.
• CORRIDOR_UNDER_MAINTENANCE 403 (docs(spec): add CORRIDOR_UNDER_MAINTENANCE 403 code #1248): the backend returns it only behind a per-platform gate (webdev #39409). The existing sandbox-suffix entry already mentions it.
• Dashboard maker/checker (webdev #39499): both gates are off by default.
• Other work: internal ops, billing, provider integration, fee, and alerting changes (for example, the go-live review tooling and fee configs), plus CI and test work. Sidebar icons (Add sidebar icons for Periodic Statements and Embedded Care #1241). Sandbox fixes with no API change.
• Outside this window and not in the changelog: risk score ceilings (feat(cards): add network risk score ceilings to the API #1216), agent chain-send receiving lock (Agents: allow a receiving-side lock on agent chain-send quotes #1227), and agent phone number pre-verification (Agent API: allow a phone number with pre-verification identity details #1224). These merged before 2026-10-26. Please say whether they should get entries.

Test plan

• Checked that every endpoint, field, enum value, and docs link in the new entries exists in openapi/ and mintlify/ on main.
• make lint-markdown fails with Missing script: "lint:markdown". The repo has no such npm script, so the markdown lint did not run.

---

Generated by Claude Code

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
Grid	🟢 Ready	View Preview	Nov 2, 2026, 5:38 PM

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments

Project	Deployment	Actions	Updated
grid-cards-demo	Ignored		Nov 2, 2026 5:37pm UTC
grid-flow-builder	Ignored		Nov 2, 2026 5:37pm UTC
grid-wallet-demo	Ignored		Nov 2, 2026 5:37pm UTC

[greptile-apps]

Confidence Score: 5/5

[Low impact] The changelog appears safe to merge; no actionable issue was established.

Summary

Adds nine announcements at the top of the existing October 2026 changelog:

• Card spending limits use rules managed through a dedicated endpoint.
• Card users can read disputes on their transactions.
• API errors identify why Grid refused a request.
• Exchange rates say whether a payout corridor is available.
• SWIFT payout destinations include a reference banks can use to trace the wire.
• Identity checks accept residence permits.
• Customers can be created from reusable KYC share tokens.
• Rule-based accounts can hold USDC and USDT.
• ACH pull guides explain funding accounts from US bank accounts.

The entries agree with the API sources and linked guides.

Author acknowledgments: pengying explicitly requested confirmation of customer-share rollout timing and partner scope, dispute endpoint deployment, crypto account availability, velocity-limit migration deployment and customer notice, and ACH pull availability. These acknowledged rollout questions were not reported as new findings.

_{Reviews (1) · Last reviewed commit: "docs: changelog for week of 2026-11-02" · Reviewed by Greptile}