Integration · Square

Square POS integration for restaurant groups

Connect Square POS to your ordering app, master menu, loyalty and franchise reports. Square's API is open to any developer, so the work is in the data model, not in getting access.

Takes two minutes. An engineer reads it, and Max replies within 1 business day.

API
REST, webhooks, OAuth 2
Access
Self-serve, full sandbox
Versions
Dated, 12 months' deprecation
Markets
US, CA, UK, IE, AU, JP, FR, ES

In short

A Square POS integration connects Square to other systems through its REST APIs: Orders, Catalog, Customers, Loyalty, Inventory and Labor. Access is self-serve: a developer account, a full sandbox and OAuth consent from each restaurant. Orders paid with a non-Square provider carry a 1% fee. Square versions its API by date and deprecates with at least 12 months' notice. dev.family builds Square connectors for multi-location groups and runs them under an SLA.

What data moves

What a Square integration moves

Read means we can get it from Square. Write means we can send it to Square.

ObjectReadWriteWhat the API supports
Catalog: items, prices, modifiersYesYesCatalog API, per location
OrdersYesYesPaid orders with fulfillment details appear in the Dashboard order manager; 1% fee with non-Square payments
Customers and loyaltyYesYesCustomers and Loyalty APIs; Square Loyalty runs in US, CA, UK, IE, AU, FR, ES
InventoryYesYesStock counts per location
LaborYesYesTeam members, timekeeping and shifts
Payments and salesYesPartlyPayments run through Square processing; sales data comes from orders and payments

Common setups

How groups connect Square

  • Own app into Square

    Your appSquareKitchen

    Orders from your app land in the right Square location with pickup or delivery details.

  • One menu, two POS

    SquareMaster menuToast

    Brands on Square and brands on Toast read one item list.

  • Delivery into Square

    Delivery app orders and couriers connect through middleware or directly.

API access

How Square API access works

Square's API is open. A developer account gives sandbox and production credentials, and each restaurant connects through OAuth. Access tokens last 30 days and refresh in the background. Webhook subscriptions are set up with the account's own token.

A listing in the Square App Marketplace is optional. It adds partnership terms, an integration check and QA, and it matters for software companies that sell to many Square sellers, not for a group connecting its own locations.

Docs developer.squareup.com · release notes at developer.squareup.com/docs/release-notes · checked November 9, 2026

What we need from you

  • Owner or admin consent for the Square account
  • Which locations and brands to connect
  • Your payment setup: Square or another provider
  • A test location

Getting access:

same day: developer credentials are self-serve, and the restaurant approves OAuth.

Not sure what your contract allows? Send us the systems and the data you need. We'll tell you which access route fits and what the connector involves.

Get a scope estimate

Platform limits

Where Square integrations break

  • Unpublished rate limits. Square doesn't publish request limits and returns a rate-limit error when you hit one. Bulk catalog syncs for many locations need backoff.

  • Duplicate and out-of-order webhooks. Square retries webhooks for up to 24 hours with a 10-second timeout, may send the same event twice and doesn't guarantee order. Deduplicate on the event ID.

  • The 1% Orders fee. Orders created through the API and paid outside Square cost 1% per transaction. Check it against your payment setup before you design the flow.

  • Version pinning. Each app is pinned to a dated API version. Upgrading is your job; retired endpoints return an error after the deprecation period.

Run

Who fixes it when the platform changes its API

  • Monitoring

    We check the connector against the live API every day and log every failed call.

  • Versions

    We move the connector to new dated API versions before the old ones are retired.

  • Alerts

    Lost or stuck orders page the on-call engineer, who fixes them under the SLA.

Questions

Didn't find your answer? Ask on the call.

  • Yes. Any developer can sign up at developer.squareup.com, get sandbox credentials and build against Square's REST APIs. A restaurant connects your app to its account through OAuth. You only need Square's review if you want to list an app on the Square App Marketplace.

  • Orders, the item catalog with prices and modifiers, customers, loyalty, inventory and team labor all have APIs. Orders created through the API show up in the Square Dashboard order manager once they're paid and carry fulfillment details.

  • Square doesn't charge for API calls, but sellers pay processing on Square payments, and orders created through the Orders API and paid with a non-Square payment provider carry a 1% fee per transaction.

  • One agency estimate puts a first Toast or Square connector at $3,000–8,000 and two to four weeks (Cadence, May 8, 2026). A group with several brands, a master menu and loyalty needs more. We fix the price per scope before the build.

  • Yes, through integrations listed in the Square App Marketplace or through middleware such as Deliverect. For a group, the harder part is keeping menus, prices and sold-out items the same on DoorDash, in your app and at the counter.

  • Yes. One Square account can hold many locations, and the APIs take a location ID. Groups that run Square in some brands and another POS in others need one item list across both.

Get a scope estimate for your Square integration

Tell us how many Square locations you run and what they need to talk to. An engineer will reply with what's possible and how long it takes.

a call with an engineer, then a fixed-price Integration Build. If the connector is part of a bigger change across brands, we start with a 2–3 week Assessment. How we work

Software vendor?We build connectors for food-tech products too, under your brand or ours. Restaurant API for software vendors

Max will reply within 1 business day with what's possible, what access we need and a rough timeline.

Who are you