HomeChevronRightIconAll postsChevronRightIconSpecial CategoriesChevronRightIconeBay Developers ProgramChevronRightIconToken, Messaging, Sandbox related issuesCreated May 5, 20260 members319 discussions braundeutschlandChallenges with Messaging API: Invalid MediaType and Conversation Errors I'm currently working on integrating the messaging API, and I've encountered a couple of frustrating issues. When I attempt to send a message with an attachment set to mediaType "IMAGE," I receive the error "M2MChatEntityClient:createMessage: Invalid conversation." However, when I change the mediaType to "PDF," "DOC," or "TXT," which are listed as valid types in the documentation, I get "Invalid mediaType value. Please see documentation for valid values." Has anyone else faced similar challenges while using this API? How did you resolve the issue? Do you have any insights into why these errors might be occurring, despite the documentation seemingly being accurate? I would appreciate any advice or shared experiences! 5 days agokrazzykatsWho Are You?Bring message smiley's back! Am I the only missing the smileys? Do I have to use the ones from my phone now? Where did all the emoticons disappear to? Maybe just weren’t getting enough attention? Please bring them back! Oh, what will we ever do without them? 😢 1 month agolast reply 1 month agoseller_news_teamThe Community site will be read-only from June 11 - 15 Read more here: https://community.ebay.com/t5/Announcements/New-Platform-Same-Amazing-Community/ba-p/35635703 1 month agoalphacards-shopunable to integrate with ebay api Hello, need a little help with a couple things related to api integration. I am currently stuck in the beginning stages. My keyset is currently disabled due to not complying with marketplace deletion/account closure notification process . When i enter marketplace deletion/account closure notification process, i am asked to enter Marketplace account deletion notification endpoint and the Verification token. I am able to enter the Marketplace account deletion notification endpoint , but I have no access to the verification token, since my account is disabled. How do i get access to my verification token, if my account is disabled? can you assist please thanks 1 month agoexperts_choiceApplication Keysets Glitch/Bug Hi all, I'm experiencing a bug where my keysets flash up for a millisecond, then disappear, and I am left with a blank page and no access, as seen in the photo. Is this a known bug, and is there a reason for it and a way to fix it? 1 month agomaroc9231Production OAuth returns invalid_client - all credentials verified correct （投稿内容を削除しました） 1 month agoaswdas12312aI want to automatically list products on eBay using a program 저는 온라인 판매자로서 eBay API를 통합하여 상품 등록, 재고키, 주문 처리 등을 자동화하는 프로그램을 개발 중입니다. 현재 귀하가 어떤 문제에 직면하고 있는지입니다. 기존 샌드박스 키 세트가 포함된 키 페이지에서 더 이상 도서실, 모래박스 및 별도 환경에서 모두 새로운 키 세트를 생성할 수 없습니다. 이 문제에 대해 eBay 고객 서비스에 문의했을 때 책임자는 계정 상태 검토 및 키 생성 권한 설정을 위해 개발자 계정 지원팀에 문의하고 안내했습니다. API 통합을 하실 수 있도록 이 문제를 처리해 주시면 감사하겠습니다. 2 months agohuxx0134sandbox key Kept receiving following error " Issue with creating keyset. Please try again later " 2 months agogeringelterThe OAuth 2.0 user-consent (3-legged) authorize endpoint PROBLEM: The OAuth 2.0 user-consent (3-legged) authorize endpoint https://auth.ebay.com/oauth2/authorize?client_id= [auth.ebay.com] &response_type=code&redirect_uri=&scope=returns HTTP 500 with the following response for ALL scope combinations(sell.inventory, basic api_scope, commerce.identity.readonly, etc.): { "error_id": "temporarily_unavailable", "error_description": "The authorization server is currently unable to handle the request.", "http_status_code": 500 } Last verified failing: 2026-05-17 01:30 CEST (HTTP 500 response via curl).Continuously broken since approximately 2026-05-15 22:00 CEST — that is~36 hours and counting. Has not resolved itself. WHAT WORKS (credentials are valid): * Client Credentials grant — token endpoint POST https://api.ebay.com/identity/v1/oauth2/token [api.ebay.com] grant_type=client_credentials returns valid access_token HTTP 200 (verified live 2026-05-17 01:30 CEST). * GDPR Marketplace Account Deletion endpoint https://booking.uwe-uli-restaurant.de/ebay/account-deletion?challenge_code= [booking.uwe-uli-restaurant.de] returns HTTP 200 with valid SHA256 challengeResponse. Configuration in Developer Portal shows COMPLETE / VERIFIED. WHAT FAILS: The user-consent 3-legged OAuth flow. Without this endpoint we cannot obtain a user access token to use the SellAPIs (sell.inventory, sell.account, sell.fulfillment). The entire sellingintegration is blocked. REQUEST: Please investigate / reset the OAuth authorize backend for this specificApp-ID. We have already verified:- App-ID and Cert-ID are valid (client_credentials grant works)- RuName is correctly configured in Developer Portal- Account Deletion compliance is GREEN- App status in Developer Portal is "Production" Repro is one curl call away — happy to provide on request. 2 months agogeringelterProduction OAuth authorize stuck on temporarily_unavailable HTTP 500 - GDPR endpoint verified Environment: Production The OAuth authorize endpoint returns HTTP 500 with this body for my Production AppID, regardless of scope: { "error_id": "temporarily_unavailable", "error_description": "The authorization server is currently unable to handle the request.", "http_status_code": 500 } Tested scopes (all return the same 500): - https://api.ebay.com/oauth/api_scope/sell.inventory - https://api.ebay.com/oauth/api_scope (basic) - https://api.ebay.com/oauth/api_scope/commerce.identity.readonly - combinations of sell.inventory + sell.account + sell.fulfillment + sell.marketing Forcing prompt=consent or different User-Agents (curl, Chrome, Firefox) doesn't change the result. Same 500. What works on the same AppID: - Client Credentials grant returns valid access_token HTTP 200 from https://api.ebay.com/identity/v1/oauth2/token - Marketplace Account Deletion endpoint returns HTTP 200 with valid SHA256 challengeResponse for any challenge_code, re-validated in the Developer Portal moments ago, status VERIFIED. What fails: - Only the 3-legged user-consent OAuth flow (authorize endpoint) is returning the 500, regardless of scope, User-Agent or browser. This started shortly after Compliance activation and has not self-resolved after multiple hours. Reading other threads here it looks like the OAuth authorize backend gets stuck per-AppID after Compliance setup in some cases. Could someone from eBay Developer Technical Support please reset the OAuth authorize service for this AppID. Client Credentials being healthy confirms the keyset itself is fine — only the user-consent pipeline is wedged. The AI Chat Assistant on the Support page diagnosed the same root cause but could not create a ticket; it directed me here. I will send the AppID and other identifying details via private message to any eBay staff member who picks this up. Thank you. 2 months agovdeals_ukCan't log in Developer account is suspended 11 months agolast reply 2 months agojosmir_8212Help getting a Production keyset for my eBay API app Hi eBay Developer Support, I’m trying to create or access a Production keyset for my app, but I’m having trouble getting it set up. My app is called ProfitFliper . I currently have Sandbox keys, but I need Production keys so I can connect real eBay accounts and continue testing/launching my integration. Can someone please help me understand what I need to complete to get a Production keyset approved or created? I’m willing to complete any required steps, including: Business/address verification Accepting the API agreement Updating app details Providing my privacy policy URL Opening a support ticket if needed Thank you for your help. 2 months ago
braundeutschlandChallenges with Messaging API: Invalid MediaType and Conversation Errors I'm currently working on integrating the messaging API, and I've encountered a couple of frustrating issues. When I attempt to send a message with an attachment set to mediaType "IMAGE," I receive the error "M2MChatEntityClient:createMessage: Invalid conversation." However, when I change the mediaType to "PDF," "DOC," or "TXT," which are listed as valid types in the documentation, I get "Invalid mediaType value. Please see documentation for valid values." Has anyone else faced similar challenges while using this API? How did you resolve the issue? Do you have any insights into why these errors might be occurring, despite the documentation seemingly being accurate? I would appreciate any advice or shared experiences! 5 days ago
krazzykatsWho Are You?Bring message smiley's back! Am I the only missing the smileys? Do I have to use the ones from my phone now? Where did all the emoticons disappear to? Maybe just weren’t getting enough attention? Please bring them back! Oh, what will we ever do without them? 😢 1 month agolast reply 1 month ago
seller_news_teamThe Community site will be read-only from June 11 - 15 Read more here: https://community.ebay.com/t5/Announcements/New-Platform-Same-Amazing-Community/ba-p/35635703 1 month ago
alphacards-shopunable to integrate with ebay api Hello, need a little help with a couple things related to api integration. I am currently stuck in the beginning stages. My keyset is currently disabled due to not complying with marketplace deletion/account closure notification process . When i enter marketplace deletion/account closure notification process, i am asked to enter Marketplace account deletion notification endpoint and the Verification token. I am able to enter the Marketplace account deletion notification endpoint , but I have no access to the verification token, since my account is disabled. How do i get access to my verification token, if my account is disabled? can you assist please thanks 1 month ago
experts_choiceApplication Keysets Glitch/Bug Hi all, I'm experiencing a bug where my keysets flash up for a millisecond, then disappear, and I am left with a blank page and no access, as seen in the photo. Is this a known bug, and is there a reason for it and a way to fix it? 1 month ago
maroc9231Production OAuth returns invalid_client - all credentials verified correct （投稿内容を削除しました） 1 month ago
aswdas12312aI want to automatically list products on eBay using a program 저는 온라인 판매자로서 eBay API를 통합하여 상품 등록, 재고키, 주문 처리 등을 자동화하는 프로그램을 개발 중입니다. 현재 귀하가 어떤 문제에 직면하고 있는지입니다. 기존 샌드박스 키 세트가 포함된 키 페이지에서 더 이상 도서실, 모래박스 및 별도 환경에서 모두 새로운 키 세트를 생성할 수 없습니다. 이 문제에 대해 eBay 고객 서비스에 문의했을 때 책임자는 계정 상태 검토 및 키 생성 권한 설정을 위해 개발자 계정 지원팀에 문의하고 안내했습니다. API 통합을 하실 수 있도록 이 문제를 처리해 주시면 감사하겠습니다. 2 months ago
huxx0134sandbox key Kept receiving following error " Issue with creating keyset. Please try again later " 2 months ago
geringelterThe OAuth 2.0 user-consent (3-legged) authorize endpoint PROBLEM: The OAuth 2.0 user-consent (3-legged) authorize endpoint https://auth.ebay.com/oauth2/authorize?client_id= [auth.ebay.com] &response_type=code&redirect_uri=&scope=returns HTTP 500 with the following response for ALL scope combinations(sell.inventory, basic api_scope, commerce.identity.readonly, etc.): { "error_id": "temporarily_unavailable", "error_description": "The authorization server is currently unable to handle the request.", "http_status_code": 500 } Last verified failing: 2026-05-17 01:30 CEST (HTTP 500 response via curl).Continuously broken since approximately 2026-05-15 22:00 CEST — that is~36 hours and counting. Has not resolved itself. WHAT WORKS (credentials are valid): * Client Credentials grant — token endpoint POST https://api.ebay.com/identity/v1/oauth2/token [api.ebay.com] grant_type=client_credentials returns valid access_token HTTP 200 (verified live 2026-05-17 01:30 CEST). * GDPR Marketplace Account Deletion endpoint https://booking.uwe-uli-restaurant.de/ebay/account-deletion?challenge_code= [booking.uwe-uli-restaurant.de] returns HTTP 200 with valid SHA256 challengeResponse. Configuration in Developer Portal shows COMPLETE / VERIFIED. WHAT FAILS: The user-consent 3-legged OAuth flow. Without this endpoint we cannot obtain a user access token to use the SellAPIs (sell.inventory, sell.account, sell.fulfillment). The entire sellingintegration is blocked. REQUEST: Please investigate / reset the OAuth authorize backend for this specificApp-ID. We have already verified:- App-ID and Cert-ID are valid (client_credentials grant works)- RuName is correctly configured in Developer Portal- Account Deletion compliance is GREEN- App status in Developer Portal is "Production" Repro is one curl call away — happy to provide on request. 2 months ago
geringelterProduction OAuth authorize stuck on temporarily_unavailable HTTP 500 - GDPR endpoint verified Environment: Production The OAuth authorize endpoint returns HTTP 500 with this body for my Production AppID, regardless of scope: { "error_id": "temporarily_unavailable", "error_description": "The authorization server is currently unable to handle the request.", "http_status_code": 500 } Tested scopes (all return the same 500): - https://api.ebay.com/oauth/api_scope/sell.inventory - https://api.ebay.com/oauth/api_scope (basic) - https://api.ebay.com/oauth/api_scope/commerce.identity.readonly - combinations of sell.inventory + sell.account + sell.fulfillment + sell.marketing Forcing prompt=consent or different User-Agents (curl, Chrome, Firefox) doesn't change the result. Same 500. What works on the same AppID: - Client Credentials grant returns valid access_token HTTP 200 from https://api.ebay.com/identity/v1/oauth2/token - Marketplace Account Deletion endpoint returns HTTP 200 with valid SHA256 challengeResponse for any challenge_code, re-validated in the Developer Portal moments ago, status VERIFIED. What fails: - Only the 3-legged user-consent OAuth flow (authorize endpoint) is returning the 500, regardless of scope, User-Agent or browser. This started shortly after Compliance activation and has not self-resolved after multiple hours. Reading other threads here it looks like the OAuth authorize backend gets stuck per-AppID after Compliance setup in some cases. Could someone from eBay Developer Technical Support please reset the OAuth authorize service for this AppID. Client Credentials being healthy confirms the keyset itself is fine — only the user-consent pipeline is wedged. The AI Chat Assistant on the Support page diagnosed the same root cause but could not create a ticket; it directed me here. I will send the AppID and other identifying details via private message to any eBay staff member who picks this up. Thank you. 2 months ago
josmir_8212Help getting a Production keyset for my eBay API app Hi eBay Developer Support, I’m trying to create or access a Production keyset for my app, but I’m having trouble getting it set up. My app is called ProfitFliper . I currently have Sandbox keys, but I need Production keys so I can connect real eBay accounts and continue testing/launching my integration. Can someone please help me understand what I need to complete to get a Production keyset approved or created? I’m willing to complete any required steps, including: Business/address verification Accepting the API agreement Updating app details Providing my privacy policy URL Opening a support ticket if needed Thank you for your help. 2 months ago
