Yahoo! Query Language
What is YQL?
The Yahoo! Query Language is an expressive SQL-like language that lets you query, filter, and join data across Web services. With YQL, apps run faster with fewer lines of code and a smaller network footprint.
Yahoo! and other websites across the Internet make much of their structured data available to developers, primarily through Web services. To access and query these services, developers traditionally endure the pain of locating the right URLs and documentation to access and query each Web service.
With YQL, developers can access and shape data across the Internet through one simple language, eliminating the need to learn how to call different APIs.
How Do I Get Started?
- Check out the YQL Console.
- Read how to access YQL from your application.
- Get your API Keys to sign your requests if you need them.
Using the API or Web Service
-
YQL Overview
YQL exposes an SQL-like SELECT syntax that is both familiar to developers and expressive enough for getting the right data. Through the SHOW and DESC commands, we enable developers to discover the available data sources and structure without opening another Web browser.
-
YQL Open Data Tables
Open Data Tables enable developers to add tables for any data on the Web to our stable of API-specific tables. Using Open Data Tables, anyone can make their data YQL-accessible. If you would like to create an Open Data Table, visit the community page at http://datatables.org.
Examples:
-
YQL Execute
Building upon Open Data Tables, the Execute element gives developers full control of how the data is fetched into YQL and how it's presented back to the user. With Execute, developers can build tables that manipulate, change, and sign the URLs to access almost any protected content. This lets YQL access and combine data across a variety of different authenticated services such as Netflix or Twitter. Developers can call multiple services and data sources within Execute to join and mash up data however they desire, letting Yahoo! do the work rather than their applications. Data can be tweaked and manipulated into an optimal format for applications to consume.
Execute elements run server-side JavaScript with E4X (native XML) support. This gives developers a fully functional language that Web developers know, and lets them do almost anything they want with the data. We've added a few new global objects to the language to enable developers to: include JavaScript libraries and code from any URL; fetch data from any URL/Web page; run other YQL commands; and perform data filtering and conversion.
Examples:
-
CSS selectors for HTML - a CSS selector table for getting data from HTML pages
use "http://yqlblog.net/samples/data.html.cssselect.xml";
select * from data.html.cssselect; -
Unified web+image search - perform a BOSS search that also returns an image from the BOSS image search for the same site and query term in a single result set
use 'http://yqlblog.net/samples/search.imageweb.xml' as searchimageweb;
select * from searchimageweb where query='pizza'
-
Usage limits
YQL has the following API usage restrictions:
Per application limit (identified by your Access Key):
- 100,000 calls per day.
Per IP limits:
- /v1/public/* 1000 calls per hour
- /v1/yql/* 10000 calls per hour
All rates are subject to change. In addition, you may also be subject to the underlying rate limits of other Yahoo and 3rd party web services.
Please contact yql-questions [at] yahoo-inc.com with requests for additional limits and information.
Support and Community
Questions and suggestions on YQL are discussed on the YQL Developer Community forum. If you have questions or need technical support, please use this forum.
Recent Blog Articles
view all
Adding value to a data feed using YQL Execute
Wed, 17 Jun 2009
Getting stock information with YQL and open data tables
Tue, 02 Jun 2009
Wed, 20 May 2009
Do it your way with execute and open data tables
Wed, 29 Apr 2009
Wed, 29 Apr 2009
YQL Forum Discussions
view all
Thu, 02 Jul 2009
Specify timeout for y.query and y.rest
Thu, 02 Jul 2009
YQL query multiple sites problem
Wed, 01 Jul 2009
Wed, 24 Jun 2009

