Here is a list of the questions we get asked most frequently, with their answers. If you don't find an answer to your question, please contact us.
Web Services provide application developers access to content and services to build new applications. For example, you can combine our data and services with those you create in a desktop application or those offered by other Web sites. With Yahoo! Web Services, more of the power of the Yahoo! network is in your hands.
Yahoo! Web Services are for developers, businesses, and researchers interested in using Yahoo! products, services, data, and content as a resource in their applications. Currently, this program is free, not subject to any SLA or uptime agreement, and subject to daily limits on query volume. If your requirements are above and beyond our standard non-commercial usage policies, please contact us and tell us how we can help your business grow.
To access Yahoo! Web Services, we require that you register and use an API Key (sometimes referred to as application ID), which is tied to your application. Your application ID must be sent with each Web Services request. Your application must also follow our Usage Policy.
As noted in the preceding answer, an Application ID is a string that uniquely identifies your application. Think of it like a User-Agent string. If you have multiple applications, you must use a different ID for each one. Get yours here.
REST stands for Representational State Transfer. Most of the Yahoo! Web Services use "REST-Like" RPC-style operations over HTTP GET or POST requests with parameters URL encoded into the request.
For more information about REST, you can start with the following:
You can use any language you like.
The best way to report bugs, outages, or unexpected behavior is by posting to the developer support forum for the Web Service or API in question.
You can request additional queries for your application via this form.
Each service may have different limits on the number of results returned by each query, as well as other variations in supported parameters. The documentation for each service specifies the default number and maximum number you can receive.
Some of our services are made available only for use in non-commercial applications. For those services, we are not able to place firm limits on what we consider "commercial use" because so many unforeseen uses are invented daily that we need to maintain a level of flexibility — especially while the program is free. That said, the following general examples show uses we consider to be commercial:
Developers can create applications that use our APIs and web services as work-for-hire for clients; however, the usage within the application itself must be approved.
To provide permission for the use of non-public user data, a user must provide consent to the third party (for example, through OAuth): A user is presented with a consent-flow interface when asked to share data with a third party through a Yahoo! API. This interface informs users of what information about them and their activities will be shared with the third party. Users have the option to retract this permission at any time by visiting their Manage Account page.
In general, the use of public user data, such as through the Updates Firehose API, does not need explicit user consent. Users are able to control what data is made public via the Manage Updates area of Yahoo! Pulse or at the location where they post an update on Yahoo!.
In general, user data may only be used on a website and/or within a mobile device application.