Skip to main content
The Early Access Programme (EAP) is the entry point for technology partners who want to build and distribute integrations with Pleo. Every partner-built integration is managed through the EAP: you register your integration intent, Pleo reviews it for technical and security alignment, and once approved, you progress from testing in Staging to a live Production integration. Pleo Partners are companies or developer teams building integrations that extend Pleo for multiple customers, typically connecting an ERP or Accounting System, and distributed through Pleo’s App Marketplace or offered as a supported partner solution. This programme isn’t for individual Pleo customers building internal tools. If that’s you, see the Pleo Customers Quickstart to get started with Standalone API Keys instead. If you are a partner, you’ll register through the EAP regardless of how many customers you plan to support, and your integration must authenticate using OAuth 2.0.

​
Authentication Requirements

EAP integrations use OAuth 2.0.

​
OAuth 2.0 (Required Default)

OAuth 2.0 is the recommended, required-by-default authentication model for partner integrations. It supports secure, scalable access across multiple customer accounts, lets customers authorise and revoke access independently, and gives your integration its own identity and audit trail.

​
Integrated API Keys (Approved Exception Only)

Integrated API Keys remain restricted and are approved only as an exception, when your ERP or system can’t support OAuth 2.0. See the Integrated API Keys Overview.

​
Standalone API Keys

You can use Standalone API Keys to explore Pleo’s APIs. We recommend you use OAuth 2.0 from the get-go, since it’s what your registered partner integration must authenticate with. EAP approval isn’t guaranteed. If you’re not approved as a Pleo Partner and you have a small number of small clients, you can use Standalone API Keys instead, which you’ll need to manage carefully. See Integration Design for Standalone API Keys. Once your clientele grows, you can register your intent again and Pleo will re-evaluate your interest.

​
What Comes Next?

Go back to the Pleo Partners Quickstart and continue with the next step to register your integration intent.

​
FAQs

​
Which authentication approach should an app serving multiple separate Pleo customers use instead of a single shared credential?

OAuth 2.0, required by default for all EAP-registered partner integrations. Integrated API Keys are allowed only as an approved exception when the partner’s ERP/system cannot support OAuth 2.0. See the Early Access Programme (EAP) for eligibility and registration details.

​
Can a multi-customer integration use Standalone API Keys instead of OAuth 2.0?

Only as a temporary fallback, not the required model. If an integration is not yet approved as a Pleo Partner through the EAP and has a small number of small clients, it can use Standalone API Keys in the meantime, managed carefully per customer. Once the partner’s clientele grows, they should re-register through the EAP and move to OAuth 2.0. See Integration Design for Standalone API Keys for how to manage this per-customer.