eBay
Connect eBay to manage listings and inventory, process orders and fulfillment, run promoted campaigns, and search products.
You end up pasting your eBay Production keyset's App ID (Client ID) and Cert ID (Client Secret) plus the RuName string from your Redirect URL settings into PopMCP, then approving the connection on eBay.
Partner application before this connector works
eBay's Buy APIs are partner-only: production access must be applied for through the eBay Partner Network and cleared by eBay's Application Growth Check, and every production keyset must first clear the mandatory Marketplace Account Deletion/Closure notification step.
- Typical wait
- Account-deletion compliance step: instant once you opt out or eBay validates your notification endpoint. Buy API partner approval: not published - eBay states there is no guarantee an application is approved
- Cost
- Free - registering for the eBay Developers Program, creating keysets and applying to the Partner Network cost nothing
- Blocked until approved
- Buy APIs (Browse beyond the open subset, Feed, Marketing, Offer, Order/checkout) return no production data until eBay Partner Network approval plus the Application Growth Check pass. Separately, a brand-new production keyset is disabled and every production call fails until you subscribe to or opt out of marketplace account deletion notifications.
- Works meanwhile
- A lot. eBay Developers Program registration and both keysets (Sandbox and Production) are self-serve and instant. The Sell APIs (Inventory, Fulfilment, Account, Marketing, Analytics) work against your own seller account with the production keyset as soon as the deletion-notification step is done - no partner approval involved. The full Sandbox environment is available for everything immediately.
Where to apply: Developer keysets: developer.ebay.com > Hi {user} > Application Keys, then resolve the account-deletion overlay by either implementing the notification endpoint or clicking the opt-out link. Buy API production access: apply via the eBay Partner Network and the Buy API production-access request linked from developer.ebay.com/api-docs/buy/buy-requirements.html; eBay then runs the Application Growth Check.
- If you opt out of account-deletion notifications you are asserting you store no eBay user data - that claim has to stay true.
- If you subscribe instead, eBay validates your HTTPS endpoint with a challenge-code handshake; a wrong verification-token/endpoint hash leaves the production keyset marked non-compliant and disabled, which is the single most common 'my production keys don't work' report.
- Buy API approval is judged on your business model, not your code - eBay explicitly says approval is not guaranteed.
- Additional keysets beyond your first require a strong technical justification and are frequently refused.
- Sandbox and Production keysets are different credentials against different hosts (api.sandbox.ebay.com vs api.ebay.com); sandbox tokens never work in production.
- eBay's developer support ticket route is often unavailable to new accounts, so a stuck keyset usually has to be chased through the developer forums.
- Setup time
- 15 min
- Auth
- OAuth authorization
- API base URL
- https://api.ebay.com
- Rate limits
- Most Sell APIs default to around 5,000 calls per day per application. Your exact ceilings are listed under Application Growth Check in the developer portal.
Before you begin
- A free eBay Developers Program account, registered at developer.ebay.com with an existing eBay user account
- An eBay seller account on the marketplace you want to manage, for the Sell APIs
- A Production keyset. New developer accounts are issued Sandbox keys first and must complete their developer account details before eBay releases Production keys
- The PopMCP callback URL shown on the eBay connect form, which goes into the RuName's 'Your auth accepted URL' field
Get your credentials
Open the Application Keys page
Sign in at developer.ebay.com, open the Hi, <your name> menu in the top right and choose Application Keysets. The direct link is developer.ebay.com/my/keys.
Application Keys
Keysets for your applications in the Sandbox and Production environments.
| Environment | App ID (Client ID) | Cert ID (Client Secret) | Status |
|---|---|---|---|
| SandboxTest data only | AcmeStor-PopMCP-SBX-****9c1d | SBX-****-a4f2 | Active |
| ProductionLive listings and orders | AcmeStor-PopMCP-PRD-****71ab | PRD-****-6e08 | Active |
Sandbox and Production are separate keysets. PopMCP defaults to Production.
Create a Production keyset if you do not have one
If the Production tab is empty, type an Application Title and click Create a keyset. Fill in your developer account contact details if eBay asks for them.
Application Keys
Keysets for your applications in the Sandbox and Production environments.
You have no Production keysets
Create one to call the live eBay APIs.
Skip this step when a Production keyset already exists.
Copy the App ID and Cert ID
On the Production keyset copy App ID (Client ID) and Cert ID (Client Secret). Leave Dev ID alone, PopMCP does not use it.
Production Keyset
Use these values to call the live eBay APIs.
- App ID (Client ID)
- AcmeStor-PopMCP-PRD-****71ab
- Dev ID
- 1f2c****-8b30-4d7e
- Cert ID (Client Secret)
- PRD-****-6e08
- Created
- Mar 4, 2026
Cert ID is a secret. Treat it like a password.
Create a RuName pointing at the PopMCP callback
Next to the Production App ID (Client ID) click User Tokens, then click Add eBay Redirect URL. Paste the PopMCP callback URL into Your auth accepted URL, tick OAuth Enabled, and click Save.
Get a Token from eBay via Your Application
Redirect URLs (RuNames) registered against AcmeStor-PopMCP-PRD-****71ab.
Saving generates the RuName, for example Acme_Store-AcmeStor-PRD-a1b2c3d4e-5f6g7h8i.
Copy the RuName and finish in PopMCP
Copy the generated RuName string, not the URL above it. In PopMCP paste the App ID, Cert ID and RuName, set Marketplace to EBAY_US, leave Environment blank, then click Connect and approve the permissions on eBay.
Connect in PopMCP
Open your workspace, choose eBay in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Auth typepreset | Create an app keyset under developer.ebay.com → Application Keys. The OAuth flow keeps your eBay login on eBay's side; we only ever store the resulting tokens. |
| App ID (Client ID)text | Your keyset's App ID (Client ID) from developer.ebay.com → Application Keys (use the Production keyset unless you picked Sandbox below). |
| Cert ID (Client Secret)secret | Your keyset's Cert ID (Client Secret), shown next to the App ID. Stored encrypted; used server-side only and never shown again.Encrypted with AES-256-GCM on save and never shown again. |
| RuName (Redirect URL name)text | The RuName string from your Redirect URL settings (NOT a URL). Its "Your auth accepted URL" must be set to the callback URL shown above. |
| Marketplacetext | The eBay marketplace this connection operates on (default EBAY_US). Sent automatically as the X-EBAY-C-MARKETPLACE-ID header + a matching language on every call. Examples: EBAY_US, EBAY_GB, EBAY_DE, EBAY_AU, EBAY_CA, EBAY_FR, EBAY_IT, EBAY_ES. |
| Environmenttext | Leave blank for a live eBay account (Production). Enter "sandbox" only if your keyset was created in eBay's Sandbox. |
https://app.popmcp.com/api/providers/ebay/callbackIn the eBay developer portal under Application Keys → User Tokens → "Get a Token from eBay via Your Application", create/edit a Redirect URL (RuName) and set its "Your auth accepted URL" to this exact URL. Then copy the RuName string into the field below.
PopMCP verifies the credential against eBay immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Permissions PopMCP requests
These are the scopes sent to eBay at authorization time.
| Scope | Why PopMCP asks for it |
|---|---|
| https://api.ebay.com/oauth/api_scope | Required by the tools this connector exposes. |
| https://api.ebay.com/oauth/api_scope/sell.inventory | Create and edit listings, offers and inventory items. |
| https://api.ebay.com/oauth/api_scope/sell.inventory.readonly | Required by the tools this connector exposes. |
| https://api.ebay.com/oauth/api_scope/sell.account | Read and update policies, store and account settings. |
| https://api.ebay.com/oauth/api_scope/sell.account.readonly | Required by the tools this connector exposes. |
| https://api.ebay.com/oauth/api_scope/sell.fulfillment | Read orders and ship or cancel them. |
| https://api.ebay.com/oauth/api_scope/sell.fulfillment.readonly | Required by the tools this connector exposes. |
| https://api.ebay.com/oauth/api_scope/sell.marketing | Run promoted listings and promotions. |
| https://api.ebay.com/oauth/api_scope/sell.marketing.readonly | Required by the tools this connector exposes. |
| https://api.ebay.com/oauth/api_scope/sell.analytics.readonly | Required by the tools this connector exposes. |
| https://api.ebay.com/oauth/api_scope/sell.finances | Read payouts and transaction reports. |
| https://api.ebay.com/oauth/api_scope/sell.payment.dispute | Required by the tools this connector exposes. |
| https://api.ebay.com/oauth/api_scope/sell.item.draft | Required by the tools this connector exposes. |
| https://api.ebay.com/oauth/api_scope/sell.item | Required by the tools this connector exposes. |
| https://api.ebay.com/oauth/api_scope/sell.reputation | Required by the tools this connector exposes. |
| https://api.ebay.com/oauth/api_scope/sell.reputation.readonly | Required by the tools this connector exposes. |
| https://api.ebay.com/oauth/api_scope/sell.stores | Required by the tools this connector exposes. |
| https://api.ebay.com/oauth/api_scope/sell.stores.readonly | Required by the tools this connector exposes. |
| https://api.ebay.com/oauth/api_scope/commerce.identity.readonly | Required by the tools this connector exposes. |
| https://api.ebay.com/oauth/api_scope/commerce.catalog.readonly | Required by the tools this connector exposes. |
| https://api.ebay.com/oauth/api_scope/commerce.notification.subscription | Required by the tools this connector exposes. |
| https://api.ebay.com/oauth/api_scope/commerce.notification.subscription.readonly | Required by the tools this connector exposes. |
Verify it worked
PopMCP redirects you to eBay's consent screen. Approve it, and the connector card returns showing Connected with your eBay username and the marketplace you chose.
Troubleshooting
invalid_client on connect
Why: The App ID and Cert ID come from different keysets, or you pasted Sandbox keys while leaving Environment blank for production.
Fix: Take both values from the same Production keyset, or type 'sandbox' in the Environment field if you deliberately used Sandbox keys.
'The redirect_uri is invalid' or unauthorized_client
Why: The RuName's 'Your auth accepted URL' does not exactly match the callback URL PopMCP shows.
Fix: Edit the Redirect URL under User Tokens so the accepted URL matches character for character, including https and any trailing path, then save and retry.
You pasted a URL into the RuName field
Why: RuName is an eBay-generated identifier, not the redirect URL itself.
Fix: Go back to User Tokens and copy the RuName string shown under the redirect entry.
The Production tab has no Create a keyset button
Why: eBay has not released Production keys for the developer account yet.
Fix: Open your account details in the developer portal, complete the contact and business information, then reload the Application Keys page.
Insufficient permissions on a Sell API call
Why: The consent grant predates a scope, or the eBay account is not a seller on that marketplace.
Fix: Disconnect and reconnect in PopMCP so the consent screen re-requests every scope, and confirm the account is a registered seller on the chosen marketplace.