API & B2B Updates
1762783632324
This release sharpens documentation and streamlines integrations across our API and B2B features. Highlights include support for additional checkout URLs (buybutton, mcp), clearer field definitions and examples (e.g., order_id as a string, updated_at behavior), and refined guidance for tax provider workflows and product custom fields. On the B2B side, we’ve updated authentication to include the Store Hash in the payload for affected endpoints and shipped targeted fixes to the Catalyst/B2B guides to speed up setup.
API
Add buybutton and mcp as valid checkout urls
Updated the documentation to include "buybutton" and "mcp" as valid checkout URLs.
Improved Automated Test Documentation and Refined Test Execution Sequence
Enhanced descriptions and clarified the testing workflow for tax provider integrations.
Update order_id field type to string in Transaction Created Webhook
Revised the Payments API webhook specification, ensuring the order_id is documented as a string.
Updated Example Value in Orders API Documentation
Improved example values in the Orders API documentation.
Update API Documentation for Product Custom Fields Parameters
Refined API docs to improve accuracy for custom field parameters for products.
Clarified Override Amount Field in Order API Documentation
Added separate definition for "override amount" in orders documentation for greater clarity.
Clarify 'updated_at' Field Description in v3 Customers API Documentation
Clarified the usage and meaning of the updated_at field in responses.
Update Invoice Email Data Structure
Refreshed invoice email documentation to match new data structure.
Modified section about configuring tax provider settings to streamline it for integrators
Streamlined tax provider API configuration docs for easier integrator onboarding.
B2B
Short-term fixes for the Catalyst/B2B guide
Various improvements and content fixes for the Catalyst and B2B setup guides.
Improved B2B Authentication Documentation
Streamlined and updated B2B authentication documentation for improved clarity and accuracy, reflecting recent changes to authentication processes.
Clarified Store Hash requirement for new authentication process.
Moved Store Hash into authentication variables instead of parameters
Removed Store Hash from requirements on authentication endpoints for generating tokens
Affected API Endpoints
POST /api/v2/auth/token
GET /api/v2/orders
POST /api/v2/products
Any other endpoints requiring Store Hash as part of authentication
Did you like this update?
![]()
![]()
![]()
Leave your name and email so that we can reply to you (both fields are optional):
