canonical: https://jentic.com/apis/paypal.com/payouts

# Paypal Payouts

Use the Payouts API to make payments to multiple PayPal or Venmo recipients. The Payouts API is a fast, convenient way to send commissions, rebates, rewards, and general disbursements. You can send up to 15,000 payments per call. If you integrated the Payouts API before September 1, 2017, you receive transaction reports through <a href="/docs/payouts/standard/reports/">Payouts Reporting</a>. The P. The API exposes 4 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically create batch payout, show payout batch details. Covers 4 operations with oauth2 authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Create batch payout
- Show payout batch details
- Cancel unclaimed payout item

## Use cases

### Payments Operations

Use the Payouts to perform payments operations programmatically. The API provides 4 endpoints covering core functionality including create batch payout, show payout batch details, show payout item details.

Example prompt: Call POST /v1/payments/payouts to create batch payout

### Automated payouts Management

Automate payouts operations by combining multiple Payouts endpoints. Agents can show payout batch details and then show payout item details in a single workflow.

Example prompt: Call GET /v1/payments/payouts/{id} to show payout batch details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Payouts endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'create batch payout', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v1/payments/payouts | Create batch payout |
| GET | /v1/payments/payouts/{id} | Show payout batch details |
| GET | /v1/payments/payouts-item/{payout_item_id} | Show payout item details |
| POST | /v1/payments/payouts-item/{payout_item_id}/cancel | Cancel unclaimed payout item |

## Key resources

- **payouts** — Use the `/payouts` resource to create a batch payout, update the status for a batch payout, show the
- **payouts-item** — Use the `/payouts-item` resource to show payout item details and cancel an unclaimed payout item.
- **payouts-statistics** — Use the `/payouts-statistics` resource to show statistics for a batch payout by date range.
- **payouts-disbursement-notifications** — Use the `payouts/disbursement-notifications` resource for status updates from <code>VENMO</code>
- **payout-application-status** — Use the `/payout-applications` resource to fetch and update payout status of the application.

## Why Jentic

- **Setup:** Wiring PayPal Payouts by hand means running its OAuth 2.0 flow, refreshing Bearer tokens, and choosing the right sandbox or live host before you can send a batch payout. Through Jentic you install once, import Payouts from the API Directory, store the client credentials once, and your agent calls it.
- **Permission scoping:** Payouts puts the payout batch id in the URL path (/v1/payments/payouts/{id}), so a rule can pin your agent to reading one payout batch or item. You choose the operations it may call, so creating a batch payout or cancelling an item is not included unless you add them.
- **Credential handling:** Your PayPal OAuth client id and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time, with token refresh handled for you. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a batch payout' or 'check a payout item status', and Jentic returns the matching Payouts operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API

## FAQ

### What authentication does the Payouts use?

The Payouts uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create batch payout with the Payouts?

Yes. Use the POST /v1/payments/payouts endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Payouts?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create batch payout through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create batch payout'. Jentic returns the matching Payouts operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Payouts have?

The Payouts exposes 4 endpoints covering payouts, payouts-item, payouts-statistics operations.

### Can I limit what my agent is allowed to do with the PayPal Payouts API?

Yes. Because you self-host Jentic One, your own rules decide which Payouts operations the agent may call, so you can grant read-only access to GET /v1/payments/payouts/{id} and GET /v1/payments/payouts-item/{payout_item_id} while withholding the write operations that create a batch payout or cancel an unclaimed item. Since the payout batch id sits in the URL path, a rule can pin the agent to one specific batch or item rather than the whole account. The OAuth client credentials stay in your Jentic One instance and are injected at execution time, so the agent only ever exercises the operations you allow.