Overview

Disclaimer This is a portfolio sample. Please keep in mind that:

• The sole purpose of this page is to showcase my understanding and practice of API documentation.

• This content is not made from scratch. It is based on the publicely available official PayPal REST APIs documentation.

• I focused on demonstrating a practical and user-friendly workflow on a best-effort basis.

• This is content is intentionally incomplete and MUST NOT be used for production projects.

• If you need a comprehensive documentation, please check the available official PayPal REST APIs documentation.

The PayPal APIs use REST and OAuth 2.0 Access Tokens for secure, standard integration, returning all data as JSON with clear HTTP response codes.

You can test US integrations with a PayPal Developer account, or immediately explore, generate client code, and import our OpenAPI specs using Postman (check out our Postman guide) without one.

Explore our REST API descriptions, generate code for your API clients, and import OpenAPI documents into compatible third-party tools.

About Integrations

You'll need a PayPal Business account to do the following:

• Go live with integrations.

• Test integrations outside the US.

Core Concepts

PayPal integrations use a client ID and client secret to authenticate API calls as described in the following table:

Cencept	Description
Client ID	A client ID identifies an app. You only need a client ID to get a PayPal payment button and standard credit and debit card fields.
Client Secret	A client secret authenticates a client ID. To call PayPal APIs, you'll exchange your client ID and client secret for an access token. Keep this secret safe.
Access Token	An access token authenticates your app when calling PayPal REST APIs.