Skip to main content
Registering an OAuth 2.0 client allows Pleo to identify Postman as the application, apply the correct redirect and scope configuration, and issue client credentials (Client ID and Client Secret) securely. This how-to is part of the Staging onboarding process and provides the redirect URIs needed for Postman when completing the Developer Partner Registration form. This guide covers Postman clients where Postman manages redirects and the token lifecycle. If your team prefers to manage the token lifecycle yourself, follow the How to Register an OAuth 2.0 Client article instead.

​
Prerequisites

  • 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 redirect URIs you need to submit in the registration form.

​
Steps

​
1. Determine your Registration Data

Provide one or both Postman variants to Pleo to register your app depending on your team’s workflow preference.

​
Example Registration

Verify all URLs and API 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:
  • Postman is registered as an OAuth 2.0 client in Pleo’s Staging environment
  • You have received a Client ID and Client Secret
  • Postman is not yet configured to use these credentials
  • API calls are not possible at this stage

​
What Comes Next?

Configure Postman →
this how-to is part of:
OAuth 2.0 Setup with Postman Workflow Guide

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