# eBay setup for PopMCP 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. - Auth: OAuth authorization - Setup time: 15 min - API base URL: https://api.ebay.com - Credentials screen: https://developer.ebay.com/my/keys - Provider docs: https://developer.ebay.com/api-docs/static/oauth-authorization-code-grant.html ## Approval required before this 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. ## 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 ### 1. Open the Application Keys page Sign in at developer.ebay.com, open the Hi, menu in the top right and choose Application Keysets. The direct link is developer.ebay.com/my/keys. Screen: https://developer.ebay.com/my/keys ### 2. 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. Screen: https://developer.ebay.com/my/keys ### 3. 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. Screen: https://developer.ebay.com/my/keys ### 4. 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. Screen: https://developer.ebay.com/my/auth ### 5. 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. ## Fields PopMCP asks for - Auth type (connectionType): 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) (clientId) [required]: 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) (clientSecret) [required]: Your keyset's Cert ID (Client Secret), shown next to the App ID. Stored encrypted; used server-side only and never shown again. - RuName (Redirect URL name) (ruName) [required]: 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. - Marketplace (marketplaceId): 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. - Environment (environment): Leave blank for a live eBay account (Production). Enter "sandbox" only if your keyset was created in eBay's Sandbox. ## Callback URL to register https://app.popmcp.com/api/providers/ebay/callback ## Scopes requested - https://api.ebay.com/oauth/api_scope - https://api.ebay.com/oauth/api_scope/sell.inventory - https://api.ebay.com/oauth/api_scope/sell.inventory.readonly - https://api.ebay.com/oauth/api_scope/sell.account - https://api.ebay.com/oauth/api_scope/sell.account.readonly - https://api.ebay.com/oauth/api_scope/sell.fulfillment - https://api.ebay.com/oauth/api_scope/sell.fulfillment.readonly - https://api.ebay.com/oauth/api_scope/sell.marketing - https://api.ebay.com/oauth/api_scope/sell.marketing.readonly - https://api.ebay.com/oauth/api_scope/sell.analytics.readonly - https://api.ebay.com/oauth/api_scope/sell.finances - https://api.ebay.com/oauth/api_scope/sell.payment.dispute - https://api.ebay.com/oauth/api_scope/sell.item.draft - https://api.ebay.com/oauth/api_scope/sell.item - https://api.ebay.com/oauth/api_scope/sell.reputation - https://api.ebay.com/oauth/api_scope/sell.reputation.readonly - https://api.ebay.com/oauth/api_scope/sell.stores - https://api.ebay.com/oauth/api_scope/sell.stores.readonly - https://api.ebay.com/oauth/api_scope/commerce.identity.readonly - https://api.ebay.com/oauth/api_scope/commerce.catalog.readonly - https://api.ebay.com/oauth/api_scope/commerce.notification.subscription - https://api.ebay.com/oauth/api_scope/commerce.notification.subscription.readonly ## Verify 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 Cause: 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 Cause: 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 Cause: 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 Cause: 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 Cause: 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. --- Source: https://www.docs.popmcp.com/docs/integrations/ebay/