Identify the check GUID and the specific selection (line item) GUID within the order that requires adjustment using the Orders API
Determine whether the scenario requires a void (item removed before close), a refund (payment already captured), or a discount applied post-close
Use the Toast API's appropriate endpoint for the action type: voiding a selection on an open check versus applying a refund on a closed check have different paths and permissions
Include a reason code or note in the adjustment payload for audit trail purposes; Toast back-office reporting surfaces these
Verify the updated check reflects the correct new total by re-fetching the order after the adjustment is applied
Known gotchas
Toast API permissions for voids and refunds are scoped separately; an integration token with read-only access cannot issue refunds — confirm the required permission scope during onboarding
Partial refunds on split checks require referencing the specific payment GUID, not the check GUID; using the wrong identifier results in a 404
Adjustments made via the API are visible in Toast reporting but may not automatically sync to connected third-party accounting integrations; verify downstream propagation
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp