canonical: https://jentic.com/apis/paypal.com/transaction-search

# Paypal Transaction Search

Use the Transaction Search API to get the history of transactions for a PayPal account. To use the API on behalf of third parties, you must be part of the PayPal partner network. Reach out to your partner manager for the next steps. To enroll in the partner program, see <a href="https://www.paypal.com/my/webapps/mpp/partner-program/global-programs">Partner with PayPal</a>. For more information abo. The API exposes 2 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically list transactions, list all balances. Covers 2 operations with oauth2 authentication.

## Scope

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

## Capabilities

- List transactions
- Access Transaction Search resources via REST API
- Access Transaction Search resources via REST API

## Use cases

### Payments Operations

Use the Transaction Search to perform payments operations programmatically. The API provides 2 endpoints covering core functionality including list transactions, list all balances.

Example prompt: Call GET /v1/reporting/transactions to list transactions

### Data Retrieval and Monitoring

Query Transaction Search endpoints to retrieve structured data for monitoring, reporting, or downstream processing. The API returns JSON responses that agents can parse directly, enabling automated data collection workflows without manual intervention.

Example prompt: Query the Transaction Search API to retrieve current data and verify the response contains expected fields

### AI Agent Integration via Jentic

AI agents discover and call Transaction Search 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 'list transactions', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/reporting/transactions | List transactions |
| GET | /v1/reporting/balances | List all balances |

## Key resources

- **transactions** — Use the `/transactions` resource to list transactions.
- **partner-transactions** — Use the `/partner-transactions` resource to list transactions.
- **balances** — Use the `/balances` resource to list balances.

## Why Jentic

- **Setup:** Wiring PayPal Transaction Search by hand means running its OAuth 2.0 flow, refreshing Bearer tokens, and choosing the right sandbox or live host before you can pull transaction and balance reports. Through Jentic you install once, import Transaction Search from the API Directory, store the client credentials once, and your agent calls it.
- **Permission scoping:** Transaction Search takes its query filters in the request, so limit the agent to the operations it needs, such as listing transactions or reading balances. You choose which of those read operations it may call, and it can call nothing else.
- **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 'list transactions in a date range' or 'read account balances', and Jentic returns the matching Transaction Search 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 Transaction Search use?

The Transaction Search 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 list transactions with the Transaction Search?

Yes. Use the GET /v1/reporting/transactions endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Transaction Search?

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 list transactions through Jentic?

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

### How many endpoints does the Transaction Search have?

The Transaction Search exposes 2 endpoints covering transactions, partner-transactions, balances operations.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which Transaction Search operations your agent may call. You can allow only the read operations it needs, such as GET /v1/reporting/transactions to list transactions or GET /v1/reporting/balances to read balances, and it can call nothing else. Your PayPal OAuth client credentials are stored encrypted in your own instance and injected at execution time, so the agent never sees the raw secrets.