Clover connector icon

Clover Connector

Embed Clover point-of-sale workflows to sync inventory, create and update orders, record payments and surface customer records inside your SaaS. Build customer-facing automations, publish them in a white-label marketplace and orchestrate multi-tenant flows with Cyclr’s embedded iPaaS.

Build with this Connector Talk to an integration expert
01

Sync inventory

Keep item catalogs and stock counts synchronized across systems.

02

Automate orders

Create and update Clover orders directly from your application workflows.

03

Reconcile payments

Pull payments and match them to orders for automated reconciliation.

04

Embedded experience

Deliver customer-facing workflows natively inside your SaaS product.

CONNECTOR OVERVIEW

What you can integrate and automate with Clover

Teams can integrate Clover merchant data — inventory items, orders, payments and customer records — and automate POS workflows such as creating orders, recording payments, syncing items and subscribing to webhook events. Cyclr connects to Clover via OAuth 2.0, runs multi-tenant orchestration, and exposes reusable workflows for in-app deployment and white-label marketplaces.

PRODUCT USE CASES

Top Use Cases for Clover Integrations

Cyclr lets developer and product teams build secure Clover integrations quickly. Use Cyclr to sync items and stock counts, create orders from your app, record payments, and receive Clover webhook events — then publish those integrations through a white-label, in-app marketplace.

Create orders in Clover from your web storefront

Create orders and add line items via Clover Orders endpoints, then attach payments so in-app purchases appear in the merchant’s POS. Use the Orders and Line Items APIs to mirror checkout carts into Clover.

Two-way item and stock synchronization

Read and update items and inventory counts using /v3/merchants/{mId}/items to keep your product catalog and Clover POS stock aligned across many merchant accounts.

Payments and reconciliation workflows

List payments and match them to orders using Payments and Orders endpoints to automate reconciliation, daily reports and export to accounting systems.

ORCHESTRATION

How Clover works with Cyclr

Cyclr sits between your SaaS product and Clover to handle authentication, govern access and orchestrate every API call per customer, at scale.

  1. 1

    Your SaaS product

    Your app requests an action for a specific customer.

  2. 2

    Cyclr orchestration

    Cyclr authenticates, applies policies and routes the request.

  3. 3

    Clover

    Clover processes the request and returns a response to your app.

Customer-specific authentication · Governed data movement · Centralized visibility and audit

CONNECTOR COVERAGE

Available connector capabilities

Explore Clover methods you can orchestrate through Cyclr.

Customers6

List Customers

Action

Gives information for every customer of a merchant.

List New Customers

Action

Gives information for every customer of a merchant since last run.

Get Customer

Action

Returns information for a single customer.

Update Customer

Action

Updates information for a single customer.

Delete Customer

Action

Deletes a single customer from a merchant.

Create Customer

Action

Creates a customer for a merchant.

Payments4

List New Payments

Action

Retrieve payment information created since last run datetime.

List Payments

Action

Retrieve payment information.

Get Payment

Action

Get information for a single payment

List Refunds

Action

Retrieve refunds for a merchant.

Orders8

Update Order

Action

Updates an Order

Create Order

Action

Create a single order from a merchant.

List Orders

Action

Returns a list of orders.

List New Orders

Action

Returns a list of orders since last run datetime.

Get Order

Action

Returns a single order.

List Updated Orders

Action

Returns a list of updated orders since last run datetime.

Delete Order

Action

Deletes a single order from a merchant.

List Line Items For Order

Action

Returns a list of line items for order.

Webhooks4

Event Webhook

Webhook

Global webhook for all Clover events. https://docs.clover.com/build/webhooks/

Customer Updated Event Webhook

Webhook

Global webhook for all Clover events. https://docs.clover.com/build/webhooks/

Customer Created Event Webhook

Webhook

Global webhook for all Clover events. https://docs.clover.com/build/webhooks/

Customer Delete Event Webhook

Webhook

Fires is customer deleted. Clover events. https://docs.clover.com/build/webhooks/

Cash3

List Cash Event for Employee

Action

Retrieve cash events filtered by employee ID

List Cash Event for Device

Action

Retrieve cash events filtered by device ID

List Cash

Action

Retrieve all cash events for merchant.

TECHNICAL DETAILS

Clover integration and API details

Review the sourced authentication and API behaviour used when configuring customer-facing Clover integrations in Cyclr.

API and authentication

API host
https://api.clover.com
Authentication
OAuth 2.0 (v2 expiring tokens) and sandbox API tokens
Credentials

OAuth client_id, client_secret, redirect_uri; access and refresh tokens; merchantId or sandbox test API token.

Method categories

Orders, Payments, Items/Inventory, Customers, Merchants, Webhooks

View vendor API documentation →

Pagination and rate limits

Pagination

List endpoints use limit and offset; default 100 items, hard maximum 1000. Time-based filters are limited to 90-day windows; page by time ranges for backfills.

Rate limits

Clover enforces per-token 16 requests/second and per-app 50 requests/second. Concurrent limits: per-token 5 and per-app 10; 429 responses include retry-after headers.

IMPLEMENTATION

Authentication at a glance

Clover uses OAuth 2.0 v2 expiring access_token and refresh_token pairs; sandbox supports merchant-specific test API tokens. New apps after October 2023 must use v2/OAuth expiring tokens.

Authentication method
OAuth 2.0 (v2 expiring tokens) and sandbox API tokens
Credential required

OAuth client_id, client_secret, redirect_uri; access and refresh tokens; merchantId or sandbox test API token.

Before you begin:

Time-based queries are capped at 90-day windows; backfills require segmented requests.

View setup guide

COMMON QUESTIONS

Frequently asked questions

It integrates merchant inventory, orders, payments and customers. You can create and update orders, record payments, sync items and subscribe to webhook events to trigger downstream workflows.

Clover uses OAuth 2.0 v2 expiring access and refresh tokens. Your app exchanges an authorization code for an access_token and refresh_token; sandbox also supports merchant-specific test API tokens.

Yes. Each merchant installs your app and provides OAuth consent; Cyclr stores and uses per-merchant tokens so you can run isolated, multi-tenant workflows per customer.

Yes. Cyclr can surface Clover API methods as governed, reusable tools in your embedded marketplace so product teams control which operations customers can run.

KEEP EXPLORING

Related resources and connectors

Documentation

Teaming up your POS and eCommerce Integrations

Read more →Product

How to develop an API – Best Practices to Follow from Cyclr Developers

Read more →Product

MCP PaaS

Read more →Related connector

Authorize.net

Related Billing/Payment connector for customer-facing integration workflows.

Related connector

SalesPad

Related Billing/Payment connector for customer-facing integration workflows.

Related connector

Aircall

Related ecommerce connector for customer-facing integration workflows.

Let Cyclr handle the integrations.

You focus on building the product your customers love.

Start building for free Get a demo