Source connector

Square connector

Square integration for databases, warehouses and BI tools

Payments and commerce platform for retail and online sellers. Datrise captures Square entities such as payments, orders, customers, catalog items, and locations, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Square API v2 (Connect v2, dated versioning e.g. `Square-Version: 2025-01-23`) authenticates with OAuth 2.0, personal access token, incremental runs key on updated_at (via the `updated_at_begin_time` query parameter on List/Search endpoints such as List Payments).

Of the 5 objects, 4 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `square_payments`) with a schema derived from the Square API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Square pipeline page, and join the waitlist to get the Square connector (ERP) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Square data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
payments	square_payments	Append-only, incremental by timestamp
orders	square_orders	Upsert by primary key, incremental on updated-at
customers	square_customers	Upsert by primary key, incremental on updated-at
catalog items	square_catalog_items	Upsert by primary key, incremental on updated-at
locations	square_locations	Upsert by primary key, incremental on updated-at

Square API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Square API v2 (Connect v2, dated versioning e.g. `Square-Version: 2025-01-23`)
Authentication	OAuth 2.0, personal access token — Production apps use OAuth 2.0 with seller-authorized access and refresh tokens; development typically uses a personal access token from the Developer Dashboard.
Pagination	cursor — List/Search endpoints return a `cursor` field when results are truncated; pass it back on the next call, it expires after 5 minutes, and default/max `limit` (e.g. 100 for List Payments) varies per endpoint.
Rate limit	Not published
Incremental cursor	updated_at (via the `updated_at_begin_time` query parameter on List/Search endpoints such as List Payments) — `begin_time` filters on `created_at` and defaults to one year back if omitted, so incremental jobs must explicitly pass `updated_at_begin_time` to also capture edited (not just new) records.
Webhooks	Yes — Square Webhooks (event notifications, e.g. `payment.updated`, `customer.deleted`)
Bulk export	No
Deletes detectable	Yes — Entity-specific `.deleted` webhook events (e.g. `customer.deleted`, `invoice.deleted`) carry a `deleted: true` flag; Catalog objects are soft-deleted and can be retrieved with `include_deleted_objects` on Batch Retrieve Catalog Objects.

Official API reference

What bites when replicating Square

Square does not publish a numeric rate limit; the only documented guidance is to retry `429 RATE_LIMITED` responses with exponential backoff plus randomized jitter.
Pagination cursors expire after 5 minutes, so a slow incremental job paging through a large `List Payments` result set can have its cursor go stale mid-run.
`GET /v2/payments` defaults to filtering on `created_at` via `begin_time` (one year back by default), not `updated_at`; you must pass `updated_at_begin_time` separately to capture edited payments.
OAuth access tokens expire 30 days after issuance regardless of activity; Square recommends renewing every 7 days via the token-renewal endpoint rather than waiting for expiry.

Compare this against every other documented API

Popular destinations for Square

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Square connector FAQ

What Square data does the connector extract?: 5 objects: payments, orders, customers, catalog items and locations. Each lands in its own table with types preserved; history-style objects (1: payments) load as append-only streams.
Is the Square integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Square data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Square → destination pair has its own page with the object-to-table mapping.

Related ERP sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Square pipeline with guided onboarding

Join the waitlist to get priority access for Square integrations with guided setup, schema-aware mapping, and production-grade incremental sync.