Paypal Transaction Search

Name: Transaction Search API
Brand: Transaction Search
Availability: InStock

✓ Official Vendor SpecPaymentsPayouts Transfersoauth22 EndpointsREST

Install Jentic One Beta

Connect the Transaction Search to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Transaction Search, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.

Capabilities

What an agent can do with Transaction Search API.

List transactions

Access Transaction Search resources via REST API

Use Cases

GET STARTED

Start building with Transaction Search API

Explore with Jentic

View OpenAPI Document

For Agents

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

Use for: I need to transactions, I want to all balances, I need to access Transaction Search programmatically, I want to integrate Transaction Search into my workflow

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

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.

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.

Search Jentic for 'list transactions', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

2 endpoints — use the transaction search api to get the history of transactions for a paypal account.

METHOD

PATH

DESCRIPTION

GET

/v1/reporting/transactions

List transactions

GET

/v1/reporting/balances

List all balances

GET

/v1/reporting/transactions

List transactions

GET

/v1/reporting/balances

List all balances

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Transaction Search API through Jentic.

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.

Paypal Transaction Search

Connect the Transaction Search to your agent

Capabilities

Use Cases

Start building with Transaction Search API

Key Endpoints

Why Jentic?

Related APIs

FAQs