Repository navigation
docs(sandbox): correct how a rule-based sweep reports an uncarriable amount - #1147
Draft
ls-bolt[bot] wants to merge 1 commit into
Draft
ls-bolt[bot] wants to merge 1 commit into
ls-bolt[bot] wants to merge 1 commit into
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
…amount The sandbox fund endpoint told integrators to fund a rule-based account with a very small amount to rehearse a SWEEP_AMOUNT_OUT_OF_RANGE failure. A small deposit no longer takes that path, so the rehearsal does not reproduce it. The two failure-reason descriptions cited the sweep rule's minimumAmount and maximumAmount as the band that decides. Neither field is populated on a returned rule, so the reasons now describe the corridor's own range. Co-Authored-By: bsiaotickchong <bsiaotickchong@users.noreply.github.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ls-bolt
Bot
force-pushed
the
10-09-sandbox-sweep-amount-prose
branch
from
October 9, 2026 01:02
1f8da8c to
6907a78
Compare
Contributor
Author
|
@greptile review |
github-actions
Bot
added
the
breaking-change
This stack of pull requests is managed by Graphite. Learn more about stacking. |
github-actions
Bot
removed
the
breaking-change
Contributor
 |
This branch was successfully deployed
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
2 participants
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
Documentation only. Three descriptions described a
SWEEP_AMOUNT_OUT_OF_RANGEfailure in terms that no longer hold.Sandbox funding.
POST /sandbox/internal-accounts/{accountId}/fundtold integrators to "fund a rule-based account with a very small amount to rehearse that path". A small deposit no longer reproduces that failure, so the instruction sent people down a path they cannot follow. The surrounding description of what happens to the balance is unchanged: a sweep the corridor cannot carry still fails, and the funds still move to the account holder's own account in the same currency.The two failure-reason descriptions.
IncomingTransactionFailureReasonandOutgoingTransactionFailureReasonboth said the rule'sminimumAmountandmaximumAmount"give the current band" for this reason. A returnedSweepRuledoes not populate either field, so that pointed readers at values they would not find. Both now describe the corridor's own range without naming fields.No enum member is added, removed, or renamed, and no behaviour changes.
Changes: 5 files
openapi/paths/sandbox/sandbox_internal_accounts_{accountId}_fund.yaml— drop the rehearsal instructionopenapi/components/schemas/transactions/IncomingTransactionFailureReason.yaml— drop theminimumAmount/maximumAmountcitationopenapi/components/schemas/transactions/OutgoingTransactionFailureReason.yaml— same, in the reason tableopenapi.yaml,mintlify/openapi.yaml— regenerated bymake buildVerification
make buildrebundles; the two generated copies are byte-identical to each other.make lint-openapipasses with 0 errors. The 909 pre-existing warnings and infos are unrelated to these files; none names a changed schema or path.🤖 Generated with Claude Code
Requested by @bsiaotickchong