Integrations / Square
Square
Square payments platform for processing card payments, managing orders, customers, product catalog items, and business locations.
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
Permissions Telara requests
- MERCHANT_PROFILE_READOAuth 2.0
- PAYMENTS_READOAuth 2.0
- PAYMENTS_WRITEOAuth 2.0
- ORDERS_READOAuth 2.0
- ORDERS_WRITEOAuth 2.0
- CUSTOMERS_READOAuth 2.0
- CUSTOMERS_WRITEOAuth 2.0
- ITEMS_READOAuth 2.0
- ITEMS_WRITEOAuth 2.0
- MERCHANT_PROFILE_WRITEOAuth 2.0
In Telara
Connect in Telara
OAuth 2.0 authorization-code connection for a Square seller in production. The requested permissions cover the catalog's locations, payments, orders, customers, and catalog read/write tools. Sandbox uses a distinct application ID and connect.squareupsandbox.com endpoints, so it is not selectable through this production app method.
In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.
Square access token — either a Personal Access Token from the Square Developer Dashboard (Sandbox or Production), or an OAuth access token obtained via Square's authorization-code flow. Both are sent identically as a bearer token; Square's own OpenAPI spec models this exact wire shape as a separate "apiKey in header" security scheme distinct from its documented oauth2 flow, confirming a static bearer token is a fully supported way to call the API outside of a full OAuth app. To target the Sandbox environment instead of production, set base_url=https://connect.squareupsandbox.com on the credential (picked up automatically) and use a Sandbox access token.
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
- Access token
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Customer | Partial — not every record the vendor holds is synced |
| Order | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Customer | Up to 1 hour | Removed records disappear when Telara next reconciles that resource |
| Order | Up to 1 hour | Removed records disappear when Telara next reconciles that resource |
Data handling
Permissions & data handling
The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.
Excluded from semantic search: Customer, Order.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty