Declare the 200 that quote and transfer creation answer

[shreyav]

POST /quotes, POST /transfer-in and POST /transfer-out have always answered 200 OK for a newly created quote or transfer; the spec declared 201 Created. The spec now matches the server. The 202 Accepted reply for a quote awaiting Strong Customer Authentication stays as declared.

Also updates the status table in the error-handling snippet, which listed quotes and transactions under 201, and adds a changelog entry.

These are the last three entries in sparkcore's handler conformance test; once this bumps into webdev the exception list goes.

make build and make lint pass. make lint-markdown fails on main as well (the lint:markdown npm script is missing).

🤖 Generated with Claude Code

https://claude.ai/code/session_01KYyhvyVNjMMDrKJqFriCE7

---

Generated by Claude Code

[mintlify]

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

Project	Status	Preview	Updated
Grid	🟢 Ready	View Preview	Oct 2, 2026, 5:33 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	Preview	Oct 2, 2026 5:32pm UTC
grid-flow-builder	Ignored	Preview	Oct 2, 2026 5:32pm UTC
grid-wallet-demo	Ignored	Preview	Oct 2, 2026 5:32pm UTC

[github-actions]

⚠️ Breaking OpenAPI changes detected

oasdiff reports 3 error / 0 warning changes to openapi.yaml.
This PR will need approval from an API reviewer before merge.

Errors (3)

• POST /quotes — removed the success response with the status 201 [response-success-status-removed].
• POST /transfer-in — removed the success response with the status 201 [response-success-status-removed].
• POST /transfer-out — removed the success response with the status 201 [response-success-status-removed].

---

Detected by oasdiff. Full report: job summary or the oasdiff-report artifact.

[greptile-apps]

Confidence Score: 4/5

[Critical risk] Changes the public API contract for quote and transfer endpoints.

The PR appears safe to merge, though the remaining quote examples should be corrected to avoid conflicting guidance.

Findings

1.  Quote examples still say 201 ▶

Fix with agent prompt

### Issue 1
mintlify/changelog.mdx:15-17
The changelog now says `POST /quotes` returns `200`, but the account-payment and crypto-funding snippets and the payout guide still label successful quote responses `201 Created`. These conflicting examples make it unclear which status readers should expect. Please align them with the corrected contract.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

The PR changes the declared successful response for quote, transfer-in, and transfer-out creation from 201 to 200 in the modular OpenAPI paths and both bundles.

• It updates the shared status table and adds a changelog entry.
• Three quote-creation examples still show 201 and should be aligned with the corrected contract.

_{Reviews (1) · Last reviewed commit: "Declare the 200 that quote and transfer ..."}

[greptile-apps]

Quote examples still say 201
The changelog now says POST /quotes returns 200, but the account-payment and crypto-funding snippets and the payout guide still label successful quote responses 201 Created. These conflicting examples make it unclear which status readers should expect. Please align them with the corrected contract.

Prompt To Fix With AI

This is a comment left during a code review.
Path: mintlify/changelog.mdx
Line: 15-17

Comment:
**Quote examples still say 201**
The changelog now says `POST /quotes` returns `200`, but the account-payment and crypto-funding snippets and the payout guide still label successful quote responses `201 Created`. These conflicting examples make it unclear which status readers should expect. Please align them with the corrected contract.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!