Finances API

Name: Finances API API
Brand: Finances API
Availability: InStock

✓ Official Vendor SpecFinanceAccountingoauth27 EndpointsREST

For Agents

Retrieve eBay seller payouts, transaction history, and funds summaries via OAuth so accounting integrations can reconcile cash movement.

Connect the Finances API to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 Finances API API.

Retrieve a specific seller payout by ID via GET /payout/{payout_Id}

List paginated seller payouts with date filters via GET /payout

Fetch a payout summary across a date range via GET /payout_summary

Read the seller's current funds balance via GET /seller_funds_summary

GET STARTED

Start building with Finances API API

Explore with Jentic

View OpenAPI Document

The eBay Finances API gives sellers programmatic access to their payouts and the underlying monetary transactions that make up each payout. Through OAuth-scoped endpoints a seller can retrieve individual payouts, list payout history, fetch a financial summary, and drill into the order, refund, and dispute transactions that net to each settlement. The API is the system of record for cash movement on a seller account and is widely used to reconcile eBay activity into accounting platforms like QuickBooks and Xero.

Use Cases

Patterns agents use Finances API API for, with concrete tasks.

★ Accounting Reconciliation

Bookkeepers reconcile eBay seller activity into QuickBooks or Xero by pulling each payout and the transactions that net to it. GET /payout lists settlements in a window, GET /payout/{payout_Id} returns the headline figures, and GET /transaction breaks the payout into orders, refunds, and fees so the journal entries line up to the cent.

Call GET /payout for the last month, iterate each payout, and pull GET /transaction filtered by payout ID to populate journal entries in the accounting system.

Seller Cash-flow Dashboard

Multi-channel sellers build cash-flow dashboards that show pending balance, recent payouts, and the trajectory of weekly settlements. GET /seller_funds_summary returns the live balance, GET /payout_summary returns the period total, and the per-payout endpoints supply the detail when the user clicks through.

Call GET /seller_funds_summary for the live balance and GET /payout_summary for the trailing 30 days, then render both in the seller dashboard.

Dispute and Refund Audit

When a seller queries why a payout came in lower than expected, support and finance teams use the Finances API to walk every deduction. GET /transaction with a transactionType filter surfaces refunds and dispute holds against a payout so the team can attribute the gap to a specific order rather than guess.

Call GET /payout/{payout_Id} for the disputed settlement, then GET /transaction filtered by that payout to list every refund and dispute deduction.

AI Agent Finance Assistant

An AI assistant for an eBay seller pulls payout figures and explains the cash impact of recent activity through Jentic. Jentic isolates the OAuth credential, surfaces the right Finances operation by intent, and validates inputs against the schema, so the agent only has to pick the time window.

Search Jentic for 'list eBay payouts', load the GET /payout schema, and execute it for the last 30 days to summarise total settlements for the seller.

Key Endpoints

7 endpoints — the ebay finances api gives sellers programmatic access to their payouts and the underlying monetary transactions that make up each payout.

METHOD

PATH

DESCRIPTION

GET

/payout

List seller payouts with date and status filters.

GET

/payout/{payout_Id}

Retrieve a specific payout by ID.

GET

/payout_summary

Aggregate payout figures across a date range.

GET

/seller_funds_summary

Get the seller's current funds balance.

GET

/transaction

List the monetary transactions that make up payouts.

GET

/transaction_summary

Aggregate transaction figures across a date range.

GET

/transfer/{transfer_Id}

Retrieve a specific transfer detail.

GET

/payout

List seller payouts with date and status filters.

GET

/payout/{payout_Id}

Retrieve a specific payout by ID.

GET

/payout_summary

Aggregate payout figures across a date range.

GET

/seller_funds_summary

Get the seller's current funds balance.

GET

/transaction

List the monetary transactions that make up payouts.

Why though Jentic?

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

Credential isolation

eBay seller OAuth tokens are stored in the encrypted Jentic vault (MAXsystem) and injected at call time. Raw seller credentials never enter the agent's context, which matters because a leaked Finances scope can read every seller payout and transaction.

Intent-based discovery

Agents search Jentic by intent (e.g., 'list eBay seller payouts' or 'get eBay funds balance') and receive the matching Finances operation with its filter schema, so the agent does not have to read eBay's REST docs.

Time to first call

Direct eBay Finances integration: 2-4 days for OAuth, scope handling, refresh tokens, and reconciliation logic. Through Jentic: under 2 hours once the OAuth credential is stored — search, load schema, execute reconciliation jobs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

eBay Identity API

Use Identity to confirm which eBay seller is authenticated before pulling Finances data.

Use first to confirm the active seller, then call Finances to retrieve payouts and transactions.

Complementary

eBay Sell Account API

Manage seller payment, fulfilment, and return policies that drive how Finances records are produced.

Use to inspect or update the seller policies that determine how payouts and refunds are calculated.

Alternative

PayPal Payouts API

Alternative settlement view for sellers that still use PayPal as a payout channel.

Choose PayPal Payouts when reconciling marketplaces that pay sellers via PayPal rather than eBay's managed payments.

FAQs

Specific to using Finances API API through Jentic.

What authentication does the eBay Finances API use?

The Finances API uses OAuth 2.0 with the seller's account scopes. The seller authorises your application, you exchange the code for an access token, and pass it as a bearer token on each call. Through Jentic the OAuth token is stored encrypted in the vault and injected at call time, so the agent never sees raw seller credentials.

Can I trigger a payout to the seller's bank account with this API?

No. The Finances API is read-only — you can list payouts, summarise them, and drill into transactions, but eBay schedules the settlement to the seller's bank itself. Use this API for reconciliation and reporting, not for moving money.

What are the rate limits for the eBay Finances API?

Specific limits are not declared in the spec but eBay applies application-level limits per call type that surface as 429 responses. For reconciliation jobs use GET /payout with date filters and back off on 429 rather than fanning out per-payout calls in parallel.

How do I list this month's payouts through Jentic?

Run pip install jentic, then search Jentic for 'list eBay payouts', load the schema for GET /payout, and execute it with the filter parameter set to a date range covering the current month. Jentic injects the OAuth bearer token from your stored credentials. Sign up at https://app.jentic.com/sign-up.

How do I see why a payout was lower than expected?

Call GET /payout/{payout_Id} for the headline figures, then GET /transaction filtered by that payout to list each refund, dispute deduction, and fee. The transaction breakdown is what reconciles to the headline payout amount.

Does the Finances API cover historical payouts back to account opening?

GET /payout supports date-range filters and returns historical payouts as far back as the underlying eBay account retention permits. For very old activity, expect the seller account itself to be the binding constraint rather than the API.