Square API

Does Square have a public API?

Yes. Square publishes a self-serve developer API covering payments, orders, catalogue, locations, team management and a Labor API for timecards and scheduled shifts. If you are building a Square app, build on that. Integuru generates a production-ready HTTP API for Square from your own login, with 14 verified actions aimed at a narrower job: the Dashboard's report views and a one-call daily cut of labor, tips and timecards per location, with no OAuth application to register.

| | Square developer API | Integuru for Square | |---|---|---| | Access | Self-serve developer account and an OAuth application | Your own Square login, no application to register | | Covers | Payments, orders, catalogue, locations, team, Labor API timecards and scheduled shifts | Dashboard report views plus daily labor, tips and timecard cuts per location | | Best for | Building a Square app | Pulling the same reports from several POS systems in one shape |

What you can do with the Square API

An operations lead running four cafés closes each day from the Dashboard: reconcile the day, check discounts and voids, and pull labor and tips for the location. The actions mirror those screens.

Reconcile the day

• get_reconciliation_summary and get_transactions_summary return the summary for a start_date to end_date range, optionally per location_id.
• list_transactions lists transactions with business_day_start and timezone so late-night sales land on the right business day, paging with page_size and next_batch_token.
• get_discounts_report and get_voids_report return the Dashboard's discount and void reports, paginated the same way; square_voids_by_date returns one location's voids for one date.

Cut labor and tips by day

• square_labor_by_date, square_tips_by_date, square_timecards_by_date and square_scheduled_shifts_by_date each take a required date and location_id.
• square_current_clocked_in_employees returns who is on the clock at a location_id for an optional business_date.

Read the catalogue and team

• square_catalog_list pages through catalogue items with cursor and page_size, optionally per location_id.
• square_team_members returns staff filtered by status and location_id; list_locations returns the ids everything else uses.

Who uses this

Restaurant back-office platforms that already ingest daily sales from Heartland, SmartTab and SpotOn through Integuru add Square here so every location arrives in the same shape and on the same maintenance contract. Tip-pooling and payroll tools run square_tips_by_date and square_timecards_by_date per location each morning. Multi-unit operators consolidating P&L pull get_reconciliation_summary nightly into the same warehouse as their Restaurant365 figures. For the restaurant-specific edition, see the Square for Restaurants guide, and for the wider workflow the restaurants industry page.

Setup notes

Integuru authenticates against app.squareup.com with your Square login, including 2FA. Call list_locations first. Dates are YYYY-MM-DD; set business_day_start and timezone on list_transactions to match the location's closeout hour. Report and transaction pagination uses next_batch_token, while the catalogue and team actions use cursor.

Get started

Install the CLI and connect your Square login:

npm install -g integuru

Or sign in at app.integuru.com, add Square, and call the same 14 actions from the dashboard. For a Dashboard report this page does not list, the Managed Service scopes and builds it against your account.