The API Report CardAPI Index
Square

Square API

SMB payments / point-of-sale / integrated commerce and banking · squareup.com

Square exposes 20-plus REST APIs and GraphQL, over 100 endpoints from Payments to Inventory, all self-serve with a free sandbox. Auth is OAuth 2.0 with scoped permissions or personal access tokens. Rate limits are undisclosed; apps see API_RATE_LIMIT_EXCEEDED without published numbers.

Last verified: October 2026Financial ServicesMCP READY
API GRADE
A
VERIFIED OCT 2026

SCORECARD

ExistenceGOODREST plus GraphQL: 20-plus APIs and over 100 endpoints, Payments through Catalog and Inventory.
AccessGOODFully self-serve with a free unlimited sandbox; the API itself costs nothing, revenue is per transaction.
CoverageGOODPayments, payouts, orders, catalog, inventory, customers, bookings, loyalty, and team management.
AuthGOODOAuth 2.0 with scoped permissions for multi-seller apps; personal access tokens for own-account use.
Docs & DXGOODFirst-party SDKs in six languages, API Explorer, per-request API Logs, and webhook replay from the dashboard.
StabilityGOODDate-stamped API versions pinned per application via the Square-Version header.
MCPGOODSquare publishes an official MCP server (beta) with a hosted remote endpoint at mcp.squareup.com and a local option, covering the full Square API surface including customers, orders, and catalog. Install and OAuth connection instructions are documented on developer.squareup.com. developer.squareup.com ↗ VERIFIED 2026-08
MORE FROM THE REPORT CARD
Supergood turns hard-to-integrate enterprise software into clean REST APIs and MCP tools: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Square scores A on Supergood's API Report Card. Square exposes 20-plus REST APIs and GraphQL, over 100 endpoints from Payments to Inventory, all self-serve with a free sandbox. Auth is OAuth 2.0 with scoped permissions or personal access tokens. Rate limits are undisclosed; apps see API_RATE_LIMIT_EXCEEDED without published numbers.

Tried to integrate with Square?
SOURCES
Webhook delivery is at-least-once with up to 11 retries over 24 hours, handlers must be idempotent; Square recently shortened the retry window from 48h/19 attempts to 24h/11 developer.squareup.com ↗
Order and Payment webhooks can arrive out of order or duplicated, particularly during high-volume promotional periods developer.squareup.com ↗
Rate limits are not publicly documented, apps hit `API_RATE_LIMIT_EXCEEDED` without a `Retry-After` predictable value drdroid.io ↗
OAuth permission model requires the seller to grant each scope individually; missing a scope silently disables webhook delivery for that resource developer.squareup.com ↗
Catalog API uses a complex object graph (CatalogObject + CatalogItem + CatalogItemVariation + CatalogModifierList) that is hard to model 1:1 into typical product schemas developer.squareup.com ↗
Orders API and Payments API model the same transaction differently, developers must reconcile `Order.tenders` vs. `Payment` records for ledger correctness developer.squareup.com ↗
Reporting API is still beta with limited historical depth; serious analytics require ListPayments/SearchOrders pagination over potentially millions of rows developer.squareup.com ↗
GraphQL surface does not yet cover every REST resource, developers often mix GraphQL queries with REST mutations developer.squareup.com ↗
API version bumps are frequent (e.g., monthly changelogs) and require teams to re-pin and re-test developer.squareup.com ↗
Sandbox does not perfectly simulate production behaviors (real card-present flows, real bank payout timing, real fraud signals, real dispute lifecycle) developer.squareup.com ↗
Checkout API has hard guidelines/limitations (per-link item caps, expiration windows) that surprise teams building hosted-checkout flows developer.squareup.com ↗
Sudden account deactivations with funds held 90–180 days are the dominant complaint pattern; Square's risk team is reported as opaque and slow to release funds paymentcloudinc.com ↗
Reserves of 20–30% of card volume held 90–180 days are imposed unilaterally on perceived-risky merchants; accounts reviewed only after 6+ months smartservice.com ↗
5,000+ BBB complaints in the past 36 months, recurring themes of fund holds and inability to reach a human reviewer cardpaymentoptions.com ↗
Triggers for sudden funding holds (large ticket vs. history, volume spikes, chargeback ratio) are not disclosed to the seller in advance cardpaymentoptions.com ↗
Broad prohibited-business list (firearms, certain CBD/cannabis, adult, telemedicine controlled substances, debt-collection, MLM, gambling) causes mid-onboarding shutoffs paymentfarm.com ↗
Flat-rate pricing (2.6% + $0.10 in-person, 2.9% + $0.30 online) becomes uncompetitive vs. interchange-plus once volume exceeds ~$15K–$20K/month tech.co ↗
Customer support is largely chat/email; phone callbacks are slow and gated to specific account tiers durangomerchantservices.com ↗
Restaurant-specific features (deep menu management, coursing, KDS, online ordering routing) lag behind Toast for full-service operations expertmarket.com ↗
Hardware lock-in: Square hardware works only with Square's payment processor; switching processors requires hardware replacement jumpermedia.co ↗
Outage and downtime incidents (notably the multi-hour Sep 2023 global outage) leave sellers unable to process payments with limited offline-mode fallbacks cardpaymentoptions.com ↗