For full functionality of this site it is necessary to enable JavaScript.
Here are the instructions how to enable JavaScript in your web browser.

Knowledge base

Find the answer to your question

Advanced Search PView

Search terms
Search Type
Product
Category
Language
Format
SDK
Sort by
Direction

All of my API calls are returning HTTP 500 errors - How to Troubleshoot

  • Answer ID 1239
  • Published 04/17/2008 05:33 PM
  • Updated 10/21/2013 01:02 PM
  • Permalink https://ebaydts.com/eBayKBDetails?KBid=1239

My calls were working fine yesterday, but today I'm getting HTTP 500 errors.  What happened?


HTTP 500 errors can be returned in a number of cases.

For example, if the errors are intermitent, the cause of the problem could be on eBay's side. Please see this Knowledge Base article for specifics in this case.

However, if all your calls are failing with this error, the cause of the problem is more likely on the side of the caller.

For example, you can get HTTP 500 errors if you mismatch the Server URL (endpoint) with the technology (ex. Shopping API endpoint used for Trading API calls).  Please see this Knowledge Base article for specifics in this case.

Please confirm your token and keyset are still valid by using the API Test Tool.

Also please checked your API usage and ensure it's not excessive or problematic.


Sometimes, these errors crop up due to a networking issue or new SSL software.  If you're running on a shared host or if you have a separate IT department, it's quite possible a change was made without your knowledge.


So you may want to download simple sample code and see if you can get a response for GeteBayOfficialTime.  Try the sample code in various environments to isolate the issue :
- Against eBay sandbox and production
- From your development or QA environment
- Your home machine (to get a different network environment)

eBay sandbox may provide more debugging information.  For example :

Production : "500 read failed:"

Sandbox : "500 read failed: error:1408F10B:SSLroutines:SSL3_GET_RECORD:wrong version number"





How well did this answer your question?

Answers others found helpful

Print Email This Page Delicious Digg Facebook Reddit StumbleUpon Twitter