Skip to main content
Registering an OAuth 2.0 client allows Pleo to identify your application, apply the correct redirect and scope configuration, and issue client credentials (Client ID and Client Secret) securely. This how-to covers advanced registration, where you manage redirects and the access-token lifecycle yourself. For a simpler setup using Postman, see the How to Register an OAuth 2.0 Client (Postman) article instead.

​
Prerequisites

Before you begin:
  • You are in the process of onboarding to Pleo’s Staging environment.
  • Pleo has asked you to complete the Developer Partner Registration form.
  • This how-to provides the information you need to submit in the registration form.

​
Steps

​
1. Provide Registration Data

You provide information to Pleo in the following categories.

​
Human-Readable Information

Do not use Pleo branding or claim your app is a Pleo client.
This information is shown to end users during authorisation:

​
Pleo-Specific Information

This information allows Pleo to integrate your application into the product:

​
Technical Information

Required details to establish a secure OAuth 2.0 flow for your registered OAuth 2.0 client:
For local development, loopback redirect URIs (localhost, 127.0.0.1, [::1]) may use HTTP.
Each Pleo API defines its own set of scopes. Your registered OAuth 2.0 client can only access APIs and perform actions that correspond to the scopes you request during registration.

​
Example Registration

Verify all URLs and scopes before submitting. Incorrect redirect URIs or missing scopes commonly cause authorisation failures.

​
2. Receive Client Credentials

Do not embed the Client Secret in frontend code or distribute it. Storing secrets on client devices is not supported by Pleo.
After registration, Pleo shares your credentials securely via 1Password:

​
Result

After completing these steps:
  • Your OAuth 2.0 client is registered in Pleo’s Staging environment.
  • You have received a Client ID and Client Secret.
  • No users are authorised.
  • No access tokens exist.
  • API calls are not possible at this stage.

​
What Comes Next?

Redirect users to the authorisation endpoint →
this how-to is part of:
OAuth 2.0 Setup Workflow Guide (Manual Token Lifecycle)

​
FAQs

These terms describe different parts of how OAuth 2.0 works in the Pleo platform.The difference between an integration, application, and OAuth 2.0 client is explained in the OAuth 2.0 Concepts and Terminology section.