Chapter 15. Appendix

Error messages and trouble-shooting

The following table displays the commonly encountered BOSS API error messages and any description or resolution for that error message. Yahoo! hopes using this table helps you trouble-shoot your BOSS API implementation before you request technical support.

If you have any issues not listed below please join the Yahoo! Groups BOSS forum:

HTTP status codes Problem Description & Resolution
400 bad request Un-escaped reserved characters. Something else wrong with request (API). Check your BOSS API parameters.
401 Invalid consumer key in a request
403 invalid AppID error, access denied, Access is forbidden Possible production code errors and not client-side errors. Please retry your API query.
406 not acceptable Accept-encoding setting must be set to 'gzip'. Keep-alive must be turned off (cannot reuse port connections).
407 Proxy authentication required. Yahoo! BOSS API does not use proxy authentication. Please check your systems.
408 Your request has timed out. Please try your request again. If this problem persists, please send a message to the BOSS Yahoo! Groups forum.
414 Request-URL Too Large. URL too long for the system to process.
500 Internal server error Received when server problems occur. Please retry your query. Single letter query may also cause this error to be displayed.
503
  • Service Unavailable. Key has exceeded its configured rate limit.
  • If it's a new key, there may be a delay between approval and turn-on. Wait and retry the key again.
  • If it's an existing key that worked earlier, please wait and try again.
  • If the above does not help you resolve your issue and it repeats for long time or happens often, report the issue on the BOSS Yahoo! Groups forum.
504 Caused by server problems in Yahoo! services. Please retry your query.
No result for common queries User may be sending a spelling query instead of a web query. Please check/verify that you have chosen the correct service in your API.
Wrong language returned Please set both the region and language in your API query.

Table of Contents