PayPal APIs for AI Agents

PaymentsPayment ProcessingSms MessagingOfficial Vendor SpecsOAuth 2.0Agent Ready

www.paypal.com·Developer portal → developer.paypal.com

PayPal API Catalog

12 APIs across 3 product groups. All share one credential.

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring PayPal by hand means learning its OAuth 2.0 client-credentials flow, exchanging and refreshing bearer tokens, and handling the split between the Orders and Payments APIs. Through Jentic you install once, import the PayPal APIs from the API Directory, store your credentials once, and your agent calls them.

Permission scoping

Most PayPal operations put the resource id in the URL path, so a rule can pin your agent to the operations you allow, such as capturing orders and issuing refunds but never sending a payout. The reporting and collection-create endpoints do not carry a resource id in the path, so for those a rule bounds which operations the agent may call rather than a single resource.

Credential isolation

FAQs

Specific to using PayPal APIs through Jentic.

Can AI agents use PayPal APIs?

Yes. All twelve PayPal APIs have OpenAPI specifications in the Jentic API Directory, so an agent can discover and call them by intent. Through Jentic the agent searches for an operation, loads its schema, and executes it. Install Jentic One (self-hosted) from its GitHub repo to get started.

Is there a PayPal MCP server?

You do not need an MCP server to give your agent PayPal. Jentic connects the PayPal APIs directly from the API Directory: import the ones you need, store your OAuth credentials once, and your agent can create orders, issue refunds, and manage subscriptions without loading another server's tool definitions into its context.

Do I need separate credentials for each PayPal API?

No. PayPal uses one set of OAuth 2.0 credentials across all of its APIs. You create a client id and secret once, exchange them for a bearer token, and the same token is accepted by every API, differing only by scope. Through Jentic the credentials are stored encrypted and injected at execution time, so they never enter the agent's context.

Can I limit what my agent is allowed to do with PayPal?

Yes. You choose which operations the agent may call through Jentic, and most PayPal operations put the resource id in the URL path, so a rule can pin the agent to specific actions such as capturing an order but not issuing a payout. The reporting endpoints filter by query string, so for those a rule bounds which operations the agent may call rather than a single resource.

BOOK A DEMO

Start Connecting APIs to Your AI Agents

Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.

Book a Demo

For Agents

APIs12 in catalogue

Endpoints108 indexed

AuthOAuth 2.0 — 1 credential for all 12 APIs

ProvenanceOfficial OpenAPI specs

Create and capture PayPal orders, run subscriptions, send invoices, save payment methods, issue payouts, manage disputes, and subscribe to webhooks across twelve APIs with one set of OAuth credentials.

PayPal separates payments into focused APIs that share one credential and one account: Orders and Payments handle the one-time checkout, Subscriptions and Catalog Products handle recurring billing, and Payouts, Invoicing, and Disputes cover disbursement and post-sale handling. Because a single OAuth client covers all of them, an agent moves from taking a payment to issuing a refund to reconciling a dispute without re-authenticating against a different service.

Use for: PayPal account payments, billing, disbursement, and dispute handling

Not supported: In-person card readers, Bank account opening, Tax filing, Accounting ledgers

Credentials: Every PayPal API uses the same OAuth 2.0 credentials. You exchange one client id and secret for a bearer token at PayPal's token endpoint, and that token is accepted across all twelve APIs, differing only by the scopes granted. You create the credentials once in the developer dashboard.

All 12 PayPal OpenAPI specs are vendor-official and indexed by Jentic, kept validated and agent-ready.

PayPal exposes its payments platform as a family of REST APIs. An agent can create and capture one-time orders, run recurring subscriptions, send and track invoices, save payment methods, disburse batch payouts, manage disputes, and subscribe to event webhooks. The one-time checkout flow spans the Orders and Payments APIs, recurring billing is built on Catalog Products and Subscriptions, and every API shares one set of OAuth credentials. The specifications are PayPal's own.

Which PayPal API should I use?

I want to...	Use	Why
Take a one-time payment at checkout	Orders	Creates, authorizes, and captures a single order across wallet, card, and local payment methods.
Refund, void, or reauthorize a captured payment after checkout	Payments	Operates on the authorization and capture ids an order produces, including issuing refunds.
Charge a customer on a recurring schedule	Subscriptions	Defines billing plans and subscriptions for recurring charges on goods or services.
Define the products that subscription plans are built on	Catalog Products	Creates the product records a billing plan references.
Bill a customer with an itemized invoice	Invoices	Creates, sends, and tracks invoices that a customer pays through a hosted link.
Pay many recipients at once	Payouts	Sends batch payouts to PayPal or Venmo recipients in a single call.

Install Jentic One Beta

Connect the PayPal APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PayPal APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpaypal.com" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpaypal.com" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Once connected, ask your agent something like: “capture a PayPal order”.

What AI Agents Can Do with PayPal

Each workflow spans multiple PayPal APIs. Jentic routes each operation to the right API automatically.

Checkout with refund and dispute handling

Take a payment and handle what comes after it. The agent creates and captures an order with the Orders API, then uses the Payments API on the resulting capture id to issue a partial or full refund when needed. If a buyer opens a dispute, the agent works it through the Disputes API by providing evidence or accepting the claim. One credential covers the whole path from sale to resolution.

Example prompt:

Capture an authorized order, refund part of the capture through the Payments API, and if a dispute is opened on it, retrieve the dispute and submit evidence.

APIs used

Orders + Payments + Disputes

Recurring subscription with a saved payment method

Stand up recurring billing for a product. The agent creates a product with the Catalog Products API, saves the customer's payment method as a reusable token with the Payment Method Tokens API, and then creates and activates a billing plan and subscription with the Subscriptions API that references both. The subscription charges on schedule without the customer re-entering details.

Example prompt:

Create a product, mint a stored payment token from a setup token, create and activate a billing plan for that product, then start a subscription against the plan.

APIs used

Catalog Products + Payment Method Tokens + Subscriptions

Fulfillment and vendor payout

Complete an order, ship it, and pay a supplier. The agent captures the order with the Orders API, attaches carrier tracking with the Shipment Tracking API so the sale qualifies for seller protection, and disburses the supplier's share with the Payouts API in a single batch call. The sequence covers the money in and the money out.

Example prompt:

Capture an order, add a carrier tracking number for it through the Shipment Tracking API, and send a batch payout to the supplier, then confirm the payout batch status.

APIs used

Orders + Shipment Tracking + Payouts

Event-driven reconciliation

Keep an accounting record in step with what happens on the account. The agent subscribes to events with the Webhooks Management API, so it is notified when an order is captured, an invoice is paid, or a payout completes, and reconciles each event against the account's history with the Transaction Search API. The two together give the agent both the live signal and the ledger.

Example prompt:

Create a webhook subscribing to payment-captured and invoice-paid events, and on each event, look up the matching transactions through the Transaction Search API.

APIs used

Webhooks Management + Transaction Search

Your PayPal OAuth client id and secret are stored encrypted by your own Jentic One instance and injected at execution time, with the bearer token exchanged for you. The raw credentials never enter the agent's prompt, logs, or context.

Intent-based discovery

An agent searches by intent, for example 'refund a captured payment', and Jentic returns the matching operation from across the twelve PayPal APIs with its input schema, so the agent calls the right API without knowing which one it is.

How do I connect my agent to PayPal?

Install Jentic One on your own infrastructure from its GitHub repo, register your PayPal OAuth credentials with it once, and add the PayPal APIs from the Jentic API Directory. Your agent then searches by intent, for example 'capture a PayPal order', and Jentic returns the matching operation with its input schema.

What is the difference between the Orders API and the Subscriptions API?

Use the Orders API for one-time payments: it creates, authorizes, and captures a single order. Use the Subscriptions API for recurring charges: it defines billing plans and subscriptions that charge on a schedule. For post-sale actions on a one-time payment, such as refunds, you use the Payments API on the capture the order produced.

What can I build by combining PayPal APIs?

Common patterns chain the APIs across a transaction's life: capture an order and refund or dispute it through the Payments and Disputes APIs, or build recurring billing from Catalog Products, saved payment tokens, and Subscriptions. One set of OAuth credentials covers every API a workflow touches.

PayPal APIs for AI Agents

PayPal API Catalog

Payments9

E Commerce2

Communications1

Why Jentic?

FAQs

Start Connecting APIs to Your AI Agents

Which PayPal API should I use?

Connect the PayPal APIs to your agent

What AI Agents Can Do with PayPal

If you need a different Payments vendor