OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured APIs across the declared product scope
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
Orders and customer APIs return structured records.
Square SearchOrders reference ↗
Search orders · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
SearchOrders returns a cursor for subsequent pages.
Square SearchOrders reference ↗
cursor / limit · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
Location and query filters select orders.
Square SearchOrders reference ↗
query / location_ids · Checked 2026-10-16
Access cost barrier -
-
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
The reviewed Square route does not establish access cost barrier.
Square SearchOrders reference ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
Seller OAuth authorization grants application access to scoped data.
Square OAuth overview ↗
Overview / OAuth flows · Checked 2026-10-16
Downstream permission -
-
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
The reviewed Square route does not establish downstream permission.
Square SearchOrders reference ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 2.5/10
Named operations in a limited domain
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
CreateCustomer creates a customer profile with CUSTOMERS_WRITE.
Square CreateCustomer reference ↗
Create customer / Permissions · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
Applications obtain seller-authorized scopes through OAuth.
Square OAuth overview ↗
Overview · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
Webhook notifications and searchable eligible events support refresh.
Square Events API recovery and retention ↗
Comparison with webhooks · Checked 2026-10-16
Limit visibility -
-
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
The reviewed Square route does not establish limit visibility.
Square SearchOrders reference ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
Customer updated/deleted event types are listed in the Customers reference.
Square CreateCustomer reference ↗
Webhooks / customer.updated and customer.deleted · Checked 2026-10-16
Replay and gap recovery 7.5/10
Replay/change queries within a documented retention window
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
Enabled eligible events remain searchable for 28 days; prior authorization required.
Square Events API recovery and retention ↗
Requirements and limitations / Security considerations · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
Complete order objects can be requested and retained externally.
Square SearchOrders reference ↗
return_entries / orders · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
The reviewed Square route does not establish post-cancellation access.
Square SearchOrders reference ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
Portable scoped orders; full product/configuration recovery unverified.
Square SearchOrders reference ↗
Search orders / orders · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
Applications process seller-authorized data externally.
Square OAuth overview ↗
Overview · Checked 2026-10-16
Rights to custom logic -
-
Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route.
The reviewed Square route does not establish rights to custom logic.
Square SearchOrders reference ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Sellers authorize application scopes through OAuth. The Events API instead requires the application’s personal access token and only exposes events the app was authorized to receive when they occurred.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
SearchOrders supports location-scoped filters and cursor pagination. Customer profiles have their own permission scope; these interfaces do not establish every Square product’s availability or migration fidelity.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Seller-authorized OAuth app | OAuth 2.0 | Integration provider | No | seller grants requested oauth scopes; marketplace publication separate | 2026-10-16 |
| Application Events API history | API key | Integration provider | No | application personal token; enable events first; contemporaneous seller oauth entitlement required | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
A complete current statement of API entitlement and access-specific charges was not established. Limits vary by endpoint; a universal numeric rate quota is not credited.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
CreateCustomer requires CUSTOMERS_WRITE and supports an idempotency key. Other mutations need their own permissions and operation contracts.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Webhooks retry for up to 24 hours without delivery-order guarantees. Events must be enabled before they become searchable; disabling capture creates a gap that later enablement does not fill.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates and deletion identities documented for the stated resourcesSquare seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. Customer updated/deleted event types are listed in the Customers reference. | Square CreateCustomer reference ↗Webhooks / customer.updated and customer.deletedChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Replay/change queries within a documented retention windowSquare seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. Enabled eligible events remain searchable for 28 days; prior authorization required. | Square Events API recovery and retention ↗Requirements and limitations / Security considerationsChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Cursor-paginated order responses provide a customer-held record copy. Complete receipts, attachments, historical configuration and cancellation retrieval rights remain unresolved.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Applications can implement external business rules. Event recovery remains limited to eligible event types and the retention window (it does not replace a complete historical snapshot). Native workflow rights were not established.
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured APIs across the declared product scopeSquare seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. Orders and customer APIs return structured records. | Square SearchOrders reference ↗Search ordersChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsSquare seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. SearchOrders returns a cursor for subsequent pages. | Square SearchOrders reference ↗cursor / limitChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersSquare seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. Location and query filters select orders. | Square SearchOrders reference ↗query / location_idsChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalSquare seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. Seller OAuth authorization grants application access to scoped data. | Square OAuth overview ↗Overview / OAuth flowsChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. The reviewed Square route does not establish access cost barrier. | Square SearchOrders reference ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. The reviewed Square route does not establish downstream permission. | Square SearchOrders reference ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainSquare seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. CreateCustomer creates a customer profile with CUSTOMERS_WRITE. | Square CreateCustomer reference ↗Create customer / PermissionsChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionSquare seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. Applications obtain seller-authorized scopes through OAuth. | Square OAuth overview ↗OverviewChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksSquare seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. Webhook notifications and searchable eligible events support refresh. | Square Events API recovery and retention ↗Comparison with webhooksChecked 2026-10-16 |
| How are integration limits disclosed? | -Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. The reviewed Square route does not establish limit visibility. | Square SearchOrders reference ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsSquare seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. Complete order objects can be requested and retained externally. | Square SearchOrders reference ↗return_entries / ordersChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. The reviewed Square route does not establish post-cancellation access. | Square SearchOrders reference ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedSquare seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. Applications process seller-authorized data externally. | Square OAuth overview ↗OverviewChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Square seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. The reviewed Square route does not establish rights to custom logic. | Square SearchOrders reference ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedSquare seller-authorized Orders and Customers APIs via OAuth; application-owned Events API with a personal token and enabled event history is a separate credential route. Portable scoped orders; full product/configuration recovery unverified. | Square SearchOrders reference ↗Search orders / ordersChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Lowest-plan API entitlement and access charges
- Endpoint-specific rate budgets
- Whole-product attachments/history and cancellation retrieval
- Native workflow rights
- Deletion-event coverage beyond reviewed customer events
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.