Skip to main content
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 or Production
  • 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.

​
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) 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

​
Existing Pleo Partners

If Standalone API Key access has already been enabled:

​
Pleo Customers

​
New Pleo Customers

You can create a Pleo account via the Pleo website, however: If you believe your use case qualifies, contact Pleo using the chat option on the website.

​
Existing Pleo Customers

If Standalone API Key access was enabled for your organisation:

​
What Comes Next?

this how-to is part of:
Standalone API Key Workflow Guide

​
FAQs

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, depending on the use case)
  • Availability: Restricted access. Documentation 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 article.