---
updatedAt: 2026-03-24T12:08:58.000Z
agentTools:
  projectIndex: https://docs.clover.com/dev/llms.txt
---

# Global developer platform—Quick steps

<meta name=" description" content= "See the quick steps to use the Clover global developer platform that offers a consolidated developer experience with access to the Global Developer Dashboard." >

[block:html]
{
  "html": "<!--JIRA DS-3008; Region pill icon added to topic on 2.27.2023-->\n<!--JIRA DS-5749; Replaced: https://www.clover.com and replace it with https://www.clover.com/global-developer-home to access the global developer platform only for the North America region.-->\n<!--JIRA DS-5917; Segregated content by region and platform-->\n<!--JIRA DS-7481; 2024-Dec-18 -->\n<!--DS-7701 and DS-7673; 2025-Apr-25 - GDE is now available for all LATAM and APAC (Australia) -->"
}
[/block]

[block:html]
{
  "html": "<!--note, this content includes NA, EU, LA, and AP, even tho the label does not. this is because we cannot edit labels without modifying all the pages that reference this snippet. 191 pages.-->\n<div class=\"container-top\">\n    <!-- North America -->\n    <div class=\"container-reg\">\n        <div class=\"pill-reg\">\n            <div class=\"label-reg\">North America</div>\n        </div>\n    </div>\n \t\t<!-- Europe -->\n    <div class=\"container-reg\">\n        <div class=\"pill-reg\">\n            <div class=\"label-reg\">Europe</div>\n        </div>\n    </div>\n    <!-- Latin America -->\n    <div class=\"container-reg\">\n        <div class=\"pill-reg\">\n            <div class=\"label-reg\">Latin America</div>\n        </div>\n    </div>\n   <!-- Asia Pacific -->\n    <div class=\"container-reg\">\n        <div class=\"pill-reg\">\n            <div class=\"label-reg\">Asia Pacific</div>\n        </div>\n    </div>\n</div>\n\n<!-- Environment -->\n    <div class=\"container-env\">\n        <div class=\"pill-env\">\n            <div class=\"label-env\">Global Developer Dashboard</div>\n        </div>\n      </div>\n\n<!-- CSS moved to global stylesheet -->"
}
[/block]

The Clover global developer platform offers a consolidated developer experience with access to the [Global Developer Dashboard](https://www.clover.com/global-developer-home).

# Environment base URLs

[block:parameters]
{
  "data": {
    "h-0": "Environment",
    "h-1": "Base URL",
    "h-2": "Description",
    "h-3": "Token type",
    "0-0": "Sandbox environment",
    "0-1": "`https://apisandbox.dev.clover.com`",
    "0-2": "Use the sandbox REST API with the [Android emulator](https://docs.clover.com/dev/docs/setting-up-an-android-emulator)  or with our [Developer Kits](https://docs.clover.com/dev/docs/clover-dev-kits) and sandbox test merchants.",
    "0-3": "To test your app in the sandbox environment, you can [generate and use merchant-specific test API tokens](https://docs.clover.com/dev/docs/gdp-manage-test-merchants-accounts#create-a-merchant-specific-api-token).",
    "1-0": "Production environment",
    "1-1": "`https://api.clover.com`",
    "1-2": "Use a separate base URL in production for each of the Clover [supported markets](https://docs.clover.com/dev/docs/region-specific-features).",
    "1-3": "[Use an expiring token ](https://docs.clover.com/dev/docs/generate-expiring-tokens-using-v2-oauth-flow)(access and refresh token pair) to secure merchant data.  \n**Note: **Do not use the test merchant API tokens in the production environment."
  },
  "cols": 4,
  "rows": 2,
  "align": [
    "left",
    "left",
    "left",
    "left"
  ]
}
[/block]

***

# Access the Global Developer Dashboard

To create apps and integrations for the North America region:

1. [Create a global developer account](https://docs.clover.com/docs/gdp-create-global-developer-account).
2. Build and test your apps in the sandbox first.
   1. Install your apps on [test merchants](https://docs.clover.com/docs/gdp-manage-test-merchants-accounts) accounts. When you sign up on the global developer platform to create a developer account, Clover creates a default test merchant account for both sandbox and production environments.
   2. Create additional test merchant accounts with different settings to simulate the effects of regions, time zones, currencies, or permissions.
   3. Test your apps that interact with the Clover payment functions. The sandbox environment is connected to a test payment gateway that checks the validity of test cards and provides realistic responses to payment requests. This lets you build apps that can handle all possible responses when completing a transaction.
3. Turn off the Sandbox toggle icon to:
   1. Access the production environment.
   2. Complete the developer account verification and approval process.
   3. Re-create your app in the production environment.
   4. Test and submit your app for approval. The Clover team reviews and approves each developer account you create in the production environment. After your app is approved and published, merchants can download and install your app from the <a href="https://www.clover.com/appmarket" target="_blank">Clover App Market</a>.
   5. Monitor the status of your app approval and communicate with the Clover team from the production Developer Dashboard. For more information, see [Understand the app approval process](https://docs.clover.com/docs/developer-app-approval-archive).

***

# Sign up for the global developer experience

If you have an existing Clover developer or merchant account, keep the following in mind when signing up for the Global Developer Dashboard:

* You **cannot create** a new global developer account with an email address that is already associated with a Clover developer or merchant account, whether in sandbox or production. Attempting to register with an existing email address results in a `User already exists` error.
* You **cannot invite** team members using email addresses previously linked to any sandbox or production developer or merchant accounts.

To avoid sign-up issues, always use a **different email address** that is not already tied to any Clover account.

***