> ## 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.

# How to Get Access to Pleo Environments (Standalone API Keys)

export const WhatComesNext = ({children, href}) => <div className="mt-4">
    <a href={href} className="
        inline-flex items-center justify-center
        rounded-full
        bg-black text-white dark:bg-[#1f262b]
        px-5 py-2.5 text-sm font-medium
        no-underline border-0
        hover:bg-[#ffe6ea] dark:hover:bg-[#2b1f23]
        hover:text-black
        transition-colors
      ">
      {children} →
    </a>
  </div>;

export const WarningCallout = ({title, children, icon = "⚠️"}) => <div style={{
  backgroundColor: 'var(--recommended-bg)',
  borderLeft: '4px solid hsl(34, 91%, 60%)',
  borderRadius: '10px',
  padding: '18px 22px',
  marginBottom: '20px',
  boxShadow: '1px 1px 3px hsl(34, 91%, 60%)'
}}>
    <div style={{
  display: 'flex',
  alignItems: 'flex-start',
  gap: '14px'
}}>
      <span style={{
  fontSize: '22px',
  lineHeight: '1',
  flexShrink: 0
}}>
        {icon}
      </span>
      <div>
        {title && <div style={{
  fontSize: '16px',
  fontWeight: 600,
  color: 'var(--recommended-title)',
  marginBottom: '6px'
}}>
            {title}
          </div>}
        <div style={{
  fontSize: '14px',
  lineHeight: 1.65
}}>
          {children}
        </div>
      </div>
    </div>
  </div>;

<WarningCallout title="Availability Notice">
  Standalone API Keys are restricted and not available to all customers or partners. For availability rules and limitations, see the [Standalone API Keys Overview](/docs/current/authentication/standalone-api-keys-overview) article.
</WarningCallout>

You require access to **Staging** or **Production** before you can generate a **Standalone API Key**.

This article explains how to:

* Confirm whether you already have access
* Request or obtain access if needed
* Continue the workflow once access is available

## 1. How to Confirm Access

You have environment access if:

* You can log into the **Pleo Web App** for [Staging](https://app.staging.pleo.io/access) or [Production](https://app.pleo.io/access)
* On the main menu on the left-hand side, you see **Settings → API Keys**
* You have **Admin** or **Bookkeeper** permissions

If the **API Keys** option is not visible, and you have the required permissions, then Standalone API Key access [has not been enabled](/docs/current/authentication/standalone-api-keys-overview).

## 2. Identify Your Role

Access depends on whether you are a **Pleo Partner** or a **Pleo Customer**.

### Pleo Partners

#### New Pleo Partners

If you are onboarding as a new partner:

1. Follow the [How to Get Access to Staging (OAuth 2.0)](/docs/current/how-tos/environment-access/how-to-get-access-to-staging-oauth) article
2. During onboarding, Pleo may enable Standalone API Key access for exploration purposes
3. Once access is confirmed, continue with the [Standalone API Key Workflow Guide](/docs/current/guides/standalone-api-keys-workflow-guide#1-generate-your-standalone-api-key)

#### Existing Pleo Partners

If Standalone API Key access has already been enabled:

* Use your existing **Staging** or **Production** login
* Continue directly with the [Standalone API Key Workflow Guide](/docs/current/guides/standalone-api-keys-workflow-guide)

### Pleo Customers

#### New Pleo Customers

You can create a Pleo account via the [Pleo website](https://www.pleo.io/en), however:

* Standalone API Key access is [**not enabled by default**](/docs/current/authentication/standalone-api-keys-overview)
* Access to the [new External APIs](#faqs) is granted only in specific cases

If you believe your use case qualifies, contact Pleo using the [chat option](https://www.pleo.io/en) on the website.

#### Existing Pleo Customers

If Standalone API Key access was enabled for your organisation:

* Log into your existing Pleo environment
* Ensure you have **Admin** or **Bookkeeper** permissions
* Continue with the [Standalone API Key Workflow Guide](/docs/current/guides/standalone-api-keys-workflow-guide#1-generate-your-standalone-api-key)

***

## What Comes Next?

<WhatComesNext href="/docs/current/how-tos/api-keys/how-to-generate-standalone-api-keys">
  Generate a Standalone API Key
</WhatComesNext>

***

<div className="text-xs uppercase" style={{ fontVariant: 'small-caps' }}>
  this how-to is part of:
</div>

<div className="mt-4 flex flex-wrap gap-2">
  <a
    href="/docs/current/guides/standalone-api-keys-workflow-guide"
    className="inline-flex items-center rounded-full border border-gray-300 dark:border-gray-600 
px-3 py-1 text-xs font-medium 
bg-white dark:bg-[#1f262b] text-black dark:text-white
hover:bg-gray-100 dark:hover:bg-[#2b2f33]
transition-colors"
  >
    Standalone API Key Workflow Guide
  </a>
</div>

***

## FAQs

<Accordion title="What is the difference between legacy APIs and new APIs?">
  **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. Pleo is working on a deprecation timeline and migration plan.

  **New APIs (External API)**

  * **Base URL:** `https://external.pleo.io`
  * **Authentication:** API keys (and other authentication methods supported by the platform, including [OAuth 2.0](/docs/current/authentication/oauth/oauth-overview), depending on the use case)
  * **Availability:** Restricted access. [Documentation](/reference/api-introduction) may be publicly visible, but access is not broadly enabled by default. Standalone API keys require explicit enablement.
  * **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`

  For more context on Standalone API Keys and environment restrictions, see the [Standalone API Keys Overview](/docs/current/authentication/standalone-api-keys-overview) article.
</Accordion>

***