Retrieve sales transaction data via the BLAZE Retail API
domain: apidocs.blaze.me · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In BLAZE Retail, go to Global Settings > Company Settings > Developer Keys, add a key scoped to a specific shop, and enable the Status toggle (and Expose Sales if you need transaction data).
Send both the partner key (X-API-Key header) and the shop-level developer key (Authorization header) on every request.
List transactions with GET /api/v1/partner/transactions, optionally filtered by startDate and endDate in MM/dd/yyyy format.
Use the convenience endpoint GET /api/v1/partner/transactions/days with startDate and a days value from 1-7 instead of an explicit date range.
Fetch a single transaction's detail with GET /api/v1/partner/transactions/{transactionId}.
Retrieve a specific member's transaction history with GET /api/v1/partner/transactions/members/{memberId}/completed or /active.
Known gotchas
Date ranges are capped at 7 days; requests exceeding that span are rejected, and omitting dates defaults to the last 7 days.
Results are paginated at 100 per page; use the skip parameter to page through larger result sets.
Transaction objects carry compliance fields directly (such as traceSubmitStatus and complianceSubmitStatus) tied to state track-and-trace submission; don't assume a sale record is compliance-neutral data.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?