Ebay Charity API
Browse all Ebay APIs✓ Official Vendor SpecE CommerceStorefrontoauth22 EndpointsREST
For Agents
Search and look up nonprofit organisations registered with eBay for Charity by keyword or charity_org_id. Two read-only endpoints.
Use for: Search for animal-welfare charities registered with eBay for Charity in the US, Look up the charity with charity_org_id 12345, Find all charities matching the keyword 'cancer' on EBAY_GB, Retrieve the legal name and EIN for an eBay charity
Not supported: Does not handle charity registration, donation processing, or seller opt-in — use for searching and looking up registered eBay for Charity nonprofits only.
The eBay Charity API lets third-party applications search and look up nonprofit organisations registered with eBay for Charity, the donation programme that lets sellers route a percentage of sale proceeds to a vetted charity. Two endpoints cover the full surface — keyword search across all supported organisations on a marketplace, and detail lookup by charity_org_id — returning legal name, EIN/registration number, logo, and mission summary. Applications use it to power charity pickers in listing flows and to verify a charity reference attached to a listing or sale.
Install Jentic One Beta
Connect the Charity API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Charity 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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
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 | sh2
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 instanceJentic 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 Charity API.
Search registered eBay charities by keyword across a marketplace to populate a picker UI
Retrieve full charity details — legal name, EIN, logo, mission — by charity_org_id
Filter charity search results by registration ID to disambiguate similarly named organisations
Validate a charity reference on a listing draft before submitting it to the Inventory API
Power charity-aware checkout flows that show donation recipient details to buyers
Use Cases
Patterns agents use Charity API for, with concrete tasks.
★ Charity picker in a seller listing flow
Sellers building listings via the Inventory API need to attach a charity_org_id and a donation percentage. Listing tools call /charity_org with a search query to populate a typeahead picker, then resolve the chosen entry through /charity_org/{charity_org_id} to confirm the legal name displayed on the live listing matches what eBay holds on file.
Search /charity_org for keyword 'animal' on EBAY_US, return the top 5 results, and resolve the user's pick via /charity_org/{charity_org_id}
Donation transparency widget for buyers
Marketplaces and shopping agents that surface eBay listings can render a donation panel — 'this listing donates 10% to Charity X' — by calling /charity_org/{charity_org_id} with the ID returned on the listing. The endpoint provides the verified mission and logo, so the buyer-facing badge does not depend on free-text seller copy.
For listing item ID 123456789012 with charityId 5678, call /charity_org/5678 and render its name, mission, and logo in a donation panel
Periodic registry refresh for a CRM
Nonprofit-focused CRMs that maintain a directory of eBay-registered charities run a nightly sync — paging through /charity_org search results per marketplace and upserting changes into their database. Because the API only returns active organisations, deleted or delisted charities naturally fall out of the local mirror.
Page through /charity_org for EBAY_US with empty query and upsert every entry into the local nonprofits table
AI agent integration via Jentic
An AI agent that helps a seller list an item with a charity donation queries Jentic with 'search eBay charities by keyword'. Jentic returns the /charity_org operation, the agent loads its schema, and executes it with the seller's marketplace_id and the keyword the seller entered. The agent then resolves the picked charity_org_id via /charity_org/{charity_org_id} for confirmation before passing it to the Sell Inventory API.
Use Jentic to search 'find eBay charity by keyword', load /charity_org, execute it with q='wildlife' and marketplace_id=EBAY_US, then look up the chosen ID via /charity_org/{charity_org_id}
Key Endpoints
2 endpoints — the ebay charity api lets third-party applications search and look up nonprofit organisations registered with ebay for charity, the donation programme that lets sellers route a percentage of sale proceeds to a vetted charity.
METHOD
PATH
DESCRIPTION
GET
/charity_org
Search registered eBay charities by keyword on a marketplace
GET
/charity_org/{charity_org_id}
Retrieve full detail for a specific charity organisation
GET
/charity_org
Search registered eBay charities by keyword on a marketplace
GET
/charity_org/{charity_org_id}
Retrieve full detail for a specific charity organisation
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
eBay OAuth 2.0 Application credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens for the commerce.charity.readonly scope only — the raw client secret never enters the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'search eBay charities') and Jentic returns the /charity_org operation with q and marketplace_id parameters, so the agent calls the right endpoint without browsing eBay's docs.
Time to first call
Direct integration: 1 day for OAuth setup, marketplace-scoping logic, and pagination handling. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Charity API through Jentic.
What authentication does the Charity API use?
The Charity API uses OAuth 2.0. The two read endpoints accept an Application access token issued via the Client_Credentials grant — no user-context token is required. Through Jentic, the OAuth client credentials sit in the MAXsystem vault and the agent receives only a scoped access token for the commerce.charity.readonly scope.
Can I create or register a charity through the Charity API?
No. The API is read-only — only GET /charity_org search and GET /charity_org/{charity_org_id} detail lookup are available. Charity registration with eBay for Charity happens through eBay's nonprofit onboarding process on charity.ebay.com, not through this API.
What are the rate limits for the Charity API?
Commerce APIs share an application-level daily quota issued per partner. Use the Developer Analytics API to see the live remaining quota for the commerce.charity resource. Because both endpoints are simple lookups, most integrations stay well within the default allowance.
How do I search for a charity by keyword through Jentic?
Search Jentic for 'search eBay charities by keyword', load the /charity_org operation schema, and execute it with q (the keyword) and marketplace_id (e.g. EBAY_US). Install with pip install jentic. Sign up at https://app.jentic.com/sign-up.
Are the same charities returned on every marketplace?
No. The Charity API is marketplace-scoped — eBay for Charity registers organisations per marketplace, so a US-registered nonprofit will only appear when searching with marketplace_id=EBAY_US. Always pass an explicit marketplace_id rather than relying on a default.
GET STARTED