Select your region
Your Clover merchant region determines which API endpoints are used.
Identify your region
Select the region that matches your Clover merchant account.
- North America (US & Canada) — default region, no additional configuration needed
- Europe — select if your merchant account is on the Clover Europe platform
- Latin America — select if your merchant account is on the Clover Latin America platform
- If unsure, check the URL when signed in to the Clover Merchant Dashboard —
clover.comis North America,eu.clover.comis Europe,la.clover.comis Latin America.
Enter your Merchant ID
The Merchant ID is a 13-character alphanumeric identifier unique to your Clover business.
Find your Merchant ID
Sign in to the Clover Merchant Dashboard for your region and locate your Merchant ID in the browser URL.
- The Merchant ID is the 13-character value after
/m/in the URL - Example URL:
https://www.clover.com/dashboard/m/ABC1DEF2GHI3J(domain varies by region) - Merchant ID:
ABC1DEF2GHI3J - For sandbox:
https://sandbox.dev.clover.com/developer-home/m/ABC1DEF2GHI3J - Copy this value and paste it into the Merchant ID field.
Create an API token
Generate a merchant-specific API token in the Clover Merchant Dashboard. Sign in with an employee account that has the Admin role.
Open the API tokens page
In the Clover Merchant Dashboard, go to Settings > View all settings > Business Operations > API tokens.
- Click Get Started if this is your first token, otherwise click Create new token.
Name the token and set permissions
Enter a token name (for example, StackOne Integrations) and select the Read or Write permissions for each category the integration needs.
Copy the token
Click Create Token, then copy the generated token and paste it into the API Token field.
- Note: Permissions can be edited on the token later. Actions fail with 401 Unauthorized when the token is missing the permission they require.
Link the Account
Connect
- Click Connect.
- If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
- Once authorization is successful, you will see a confirmation popup.
Use Actions