Access the Brink API portal at brinkapiportal.brinkpos.net and review the SOAP-based API contract; note that Brink uses SOAP over HTTPS rather than REST for core POS operations
Authenticate to the Brink API service using the credentials provided during integration onboarding and call the Ordering service's CalculateOrder method to validate the order and retrieve pricing before submission
Submit the order by calling the appropriate Ordering service method with the full order payload including items, modifiers, tender type, and location identifiers
Poll the order status using the corresponding retrieval method; follow Brink's best-practice recommendation of making 5 to 10 concurrent calls with a sleep interval of 2 to 3 minutes between polling cycles
Always submit DateTime parameters in UTC format; the GetShifts call and other time-sensitive methods have built-in logic that will not return data correctly if datetime values are not in UTC
Handle errors from the API response envelope and implement a dead-letter queue for failed submissions to avoid silent order loss
Known gotchas
Brink's core POS API uses SOAP, not REST; standard REST client libraries are insufficient and a SOAP client or framework is required
DateTime values must be UTC throughout; non-UTC datetimes cause silent failures in shift and time-sensitive API calls
Brink recommends explicit concurrency limits and sleep intervals; exceeding these can result in throttling or degraded performance on the POS terminal
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