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

# Early Access Programme (EAP)

The **Early Access Programme (EAP)** is the entry point for **technology partners** who want to build and distribute integrations with Pleo.

The programme provides a structured path for partners to register their integration intent, align on technical and security expectations, and progress from early testing to a live production integration.

## What is the Early Access Programme (EAP)?

All **partner-built integrations** with Pleo are managed through the Early Access Programme (EAP).

The programme ensures that integrations:

* Meet Pleo’s technical and security standards
* Follow supported authentication and data access models
* Are suitable for use across multiple customer accounts
* Are reviewed before accessing production environments

Access to production APIs is not granted automatically and requires approval through the EAP.

## Who Is This For?

### Pleo Partners

**Pleo Partners** are companies or developer teams building integrations that extend Pleo for multiple customers.

These integrations typically:

* Connect ERP or Accounting Systems to Pleo
* Are designed for reuse across many organisations
* May be distributed through **Pleo’s App Marketplace** or offered as supported partner solutions

This programme is **not intended for individual Pleo customers building internal tools**.

## Business and Technical Requirements

Participation in the EAP is subject to the following conditions:

* **Manual Review:** All partner registrations are reviewed before production access is granted
* **Partner Scope:** Integrations must be designed for multi-customer use
* **Security Standards:** Production access must comply with Pleo’s authentication and data protection requirements

## Authentication Requirements

EAP integrations must use **OAuth 2.0** or **integrated API keys associated with a registered integration**. Standalone API keys are not supported for partner integrations in the Early Access Programme.

Pleo supports the following authentication models for partner integrations:

### OAuth 2.0 (Required Default)

* Required for all partner integrations accessing live customer data
* Supports secure, scalable access across multiple customer accounts
* Enables customers to authorise and revoke access independently
* Provides integration-level identity and auditability

OAuth 2.0 is the preferred and recommended authentication model for all partners.

### Integrated API Keys (Approved Exception Only)

Integrated API keys may be permitted where OAuth 2.0 cannot be supported due to ERP or system constraints.

These keys:

* Are issued as part of a registered integration
* Are tied to a specific partner integration identity
* Allow Pleo to track integration usage and enforce platform controls
* Require explicit approval through the Early Access Programme review process

Standalone API keys created outside of an approved integration are not supported for partner integrations.

<Note title="Authentication Requirement">
  Partner integrations must use OAuth 2.0 or integrated API keys issued for a registered integration. Standalone API keys are not supported under the Early Access Programme.
</Note>

## What Comes Next?

Once you’ve reviewed the requirements above, you can explore Pleo’s available [environments](/docs/current/getting-started/testing-and-environments) and begin onboarding in **Staging** using **OAuth 2.0**.

During the onboarding process, you’ll be asked to **register your integration intent as part of the Early Access Programme (EAP)**.

This allows Pleo to:

* Understand your integration use case
* Validate technical and security alignment
* Manage progression beyond staging to additional environments