> ## Documentation Index
> Fetch the complete documentation index at: https://developers.pleo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Pleo Customers: API Quickstart

> Who this quickstart is for, the recommended reading order to get started, and migration paths if you're on the Legacy APIs.

This section is for **individual Pleo customers** connecting their own company's systems to Pleo, for example internal tooling, exports to a data warehouse, one-off migrations, or reporting. If you're building an integration that will serve multiple customers, use the [Pleo Partners Quickstart](/docs/current/getting-started/pleo-partners-quickstart) instead.

Follow the recommended reading order below to confirm Standalone API Keys is the right integration path for you, and to see the migration pathways available if you're currently on the Legacy APIs.

## Recommended Reading Order

### Decide if an API Integration Is the Right Approach for You

<CardGroup cols={2}>
  <Card title="1. Platform Overview" icon="https://mintcdn.com/pleo-61d4d38b/0im2PqYmwpP-taWp/images/current/icons/workflow-guide-catalogue.svg?fit=max&auto=format&n=0im2PqYmwpP-taWp&q=85&s=ff32059a895f7a5f7087ed6ebb6b0312" href="/docs/current/getting-started/platform-overview" width="256" height="256" data-path="images/current/icons/workflow-guide-catalogue.svg">
    <div className="text-sm mt-2">Confirm Standalone API Keys are the right fit before you request access.</div>
  </Card>

  <Card title="2. API Overview" icon="https://mintcdn.com/pleo-61d4d38b/earhx-WV21nRUBYy/images/current/icons/api-reference.svg?fit=max&auto=format&n=earhx-WV21nRUBYy&q=85&s=2740a80ea0609139703ec7bd7149b0fb" href="/docs/current/getting-started/platform-api-overview" width="256" height="256" data-path="images/current/icons/api-reference.svg">
    <div className="text-sm mt-2">The REST API conventions and the main API surfaces available to your integration.</div>
  </Card>

  <Card title="3. Pleo MCP" icon="https://mintcdn.com/pleo-61d4d38b/earhx-WV21nRUBYy/images/current/icons/pleo-mcp-overview.svg?fit=max&auto=format&n=earhx-WV21nRUBYy&q=85&s=f999d6d938e4ad0d24ae6f1882c437b5" href="/docs/current/getting-started/pleo-mcp-quickstart" width="256" height="256" data-path="images/current/icons/pleo-mcp-overview.svg">
    <div className="text-sm mt-2">You may not need a coded integration at all if the Pleo MCP already covers your use case.</div>
  </Card>

  <Card title="4. Pre-Built Integrations" icon="https://mintcdn.com/pleo-61d4d38b/earhx-WV21nRUBYy/images/current/icons/pre-built-integrations.svg?fit=max&auto=format&n=earhx-WV21nRUBYy&q=85&s=b705529a828c6b2aa5d63a469af919e2" href="https://www.pleo.io/en/integrations" width="256" height="256" data-path="images/current/icons/pre-built-integrations.svg">
    <div className="text-sm mt-2">Check whether a ready-made connector already covers your Accounting System or HRIS before building anything custom.</div>
  </Card>
</CardGroup>

### Ready to Proceed with an API Integration?

<CardGroup cols={2}>
  <Card title="5. Standalone API Keys Overview" icon="https://mintcdn.com/pleo-61d4d38b/earhx-WV21nRUBYy/images/current/icons/access-permissions.svg?fit=max&auto=format&n=earhx-WV21nRUBYy&q=85&s=5fdc4d93616eb532eb1b1e921e7775d7" href="/docs/current/authentication/standalone-api-keys-overview" width="256" height="256" data-path="images/current/icons/access-permissions.svg">
    <div className="text-sm mt-2">Understand Standalone API Keys and how they work with your organisation.</div>
  </Card>

  <Card title="6. How to Get Access to Environments" icon="https://mintcdn.com/pleo-61d4d38b/-zfbxbcW6wX8Tnmv/images/current/icons/bounding-box.svg?fit=max&auto=format&n=-zfbxbcW6wX8Tnmv&q=85&s=12be80375a4506ffa3df11f52f3afe17" href="/docs/current/how-tos/environment-access/how-to-get-access-to-all-env-standalone-api-keys" width="256" height="256" data-path="images/current/icons/bounding-box.svg">
    <div className="text-sm mt-2">Confirm or request access to Staging or Production before generating a key.</div>
  </Card>

  <Card title="7. Standalone API Key Workflow Guide" icon="https://mintcdn.com/pleo-61d4d38b/0im2PqYmwpP-taWp/images/current/icons/workflow-guide-catalogue.svg?fit=max&auto=format&n=0im2PqYmwpP-taWp&q=85&s=ff32059a895f7a5f7087ed6ebb6b0312" href="/docs/current/guides/standalone-api-keys-workflow-guide" width="256" height="256" data-path="images/current/icons/workflow-guide-catalogue.svg">
    <div className="text-sm mt-2">Generate your key in the Pleo Web App and make your first authenticated API call.</div>
  </Card>
</CardGroup>

## Migrate from the Legacy APIs to the New APIs

Pleo is migrating away from the Legacy APIs, so if your organisation currently uses them, start planning your move to the new External API platform. See the [Deprecation & Migration Guides](/deprecation/migration-guides) for available migration paths.

New customers are only given access to the new API Keys.

<Accordion title="What is the difference between legacy APIs and new APIs?" defaultOpen>
  **Legacy APIs (OpenAPI)**

  * **Base URL:** `https://openapi.pleo.io`
  * **Authentication:** API tokens (legacy tokens)
  * **Availability:** Intended for existing/legacy use cases. Access can depend on your account setup and entitlements.
  * **Lifecycle:** Deprecated. See the [deprecation timeline and migration plan](/deprecation/overview).

  **New APIs (External API)**

  * **Base URL:** `https://external.pleo.io`
  * **Authentication:** [API keys](/docs/current/authentication/standalone-api-keys-overview) (and other authentication methods supported by the platform, including [OAuth 2.0](/docs/current/authentication/oauth/oauth-overview), depending on the use case)
  * **Availability:** Available without restriction, but may need to be [enabled for your organisation](/docs/current/how-tos/environment-access/how-to-get-access-to-all-env-standalone-api-keys).
  * **What to expect:** Newer platform surface and improved structure, but not guaranteed feature parity with legacy APIs yet.

  **Important:**

  * Legacy API tokens **will not work** on `external.pleo.io`
  * New API keys **will not work** on `openapi.pleo.io`
</Accordion>

## Environments

Pleo provides two environments, **Staging** and **Production**. Unlike Pleo Partners, who must complete a staging-first review through the Early Access Programme before reaching Production, you can [generate](/docs/current/how-tos/api-keys/how-to-generate-standalone-api-keys) a Standalone API Key for either environment directly:

* **Staging:** a sandbox with test data, useful for exploring the API before touching real data.
* **Production:** your live company data.

## What Comes Next?

Once you've generated your Standalone API Key and made a successful test call, explore the [Platform Capabilities & Concepts Catalogue](/docs/current/platform/platform-capabilities-overview) to understand the different workflows, such as exports, imports, and multi-entity setups, that you can build with the API.