PAR Brink API
Brink exposes a SOAP/XML API with published WSDLs; there is no REST, JSON, or webhook surface. Access is partner-gated through api.support@partech.com with per-brand certification and per-location tokens. Integrations poll Sales2 for new orders since nothing pushes events.
Frequently asked questions
PAR Brink scores F on the API Report Card. Brink exposes a SOAP/XML API with published WSDLs; there is no REST, JSON, or webhook surface. Access is partner-gated through api.support@partech.com with per-brand certification and per-location tokens. Integrations poll Sales2 for new orders since nothing pushes events.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly.
PAR Brink POS is the flagship enterprise, cloud-based point-of-sale platform from PAR Technology Corporation (NYSE: PAR), a 50+ year old restaurant technology vendor headquartered in New Hartford, NY.
Vertical: POS / Hospitality (enterprise restaurant POS). Cloud-managed POS configuration, menu, pricing, tax, and promo updates pushed down to thousands of locations from a central HQ. Order entry on PAR EverServ / Helix terminals, drive-thru, kiosk, and handheld.
7/10 within enterprise restaurant POS. ~9,000 locations and a dominant share of the top-500 chains crowd Brink into the top three enterprise QSR POS platforms alongside Oracle MICROS Simphony and NCR Aloha.
Yes - Brink is the system of record for transaction-level sales, payment, labor, and configuration data at 9,000+ enterprise restaurant locations including Burger King, Arby's, Dairy Queen, Five Guys, Sweetgreen, CKE, and Inspire Brands.
Brink Software was founded in 2007 and acquired by PAR Technology in September 2014 (~19 years old). The product itself is cloud-managed and was one of the first true cloud POS platforms in enterprise QSR, predating Toast by several years.
SOAP/XML only - no REST, no JSON, no GraphQL, requiring partners to maintain SOAP client tooling and XML schema bindings in an industry that has moved to REST. Strict field-order requirements: 'XML must be structured according to the order published in the WSDL, and you must not change the order of the fields in the request sent, or it will fail' - any drift breaks integrations silently. Full sourced list under Sources below.
Common alternatives include Oracle MICROS Simphony, NCR Aloha (NCR Voyix), Toast, Square for Restaurants, Lightspeed Restaurant, Revel Systems. Graded alternatives appear under "More from the report card" below.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.
Yes. Supergood maintains an unofficial PAR Brink API and MCP server so AI agents and internal tools can read and write PAR Brink data. See the PAR Brink integration docs at supergood.ai/docs/par-brink-api.