1. What type of advertising are you interested in?* (select all that apply)
| Search Marketing | Mobile Search Marketing |
| Mobile Display / Banner Advertising | Display/Banner/Video Advertising |
2.What is your monthly advertising budget? |
Target Customers by Geographic LocationDisplay your ad to customers throughout the entire market, or select specific regions or cities.
Yahoo! Search offers an array of web services to provide you with access to our investments in search technology and infrastructure. Developers and site owners can also use web services to enhance Yahoo! Search results.
BOSS (Build your Own Search Service) and other web services give developers and start-ups access to our web-scale investments in search technology. See what's available and how to get started:
BOSS provides API access to Yahoo!'s web, news, and image search technology. Unlike other search APIs, developers can use BOSS technology with very few restrictions.
To get started, visit the BOSS page to learn more about what BOSS can do, apply for an API key, and read the documentation.
Our recently released Content Analysis Web Service detects entities/concepts, categories, andrelationships within unstructured content. It ranks those detected entities/concepts by their overall relevance, resolves those if possible into Wikipedia pages, and annotates tags with relevant meta-data. Please give our content analysis service a try to enrich your content.
The Term Extraction Web Service provides a list of significant words or phrases extracted from a body of content. Note: This service will no longer be supported. Please migrate to the Content Analysis Web Service.
The Geocoding Web Service allows you to find the specific latitude and longitude for an address. You can use this service to geocode your points in advance or forego it altogether with built-in geocoding in our AJAX and Flash APIs.
This API has been deprecated (that is, no longer recommended for use by new developers). A new geocoding API called Yahoo! PlaceFinder is now available and provides more features than this API, including reverse geocoding (translating coordinates into street addresses) and WOEID support. Current developers using this API are encouraged to migrate to PlaceFinder.
http://local.yahooapis.com/MapsService/V1/geocode
See information on constructing REST queries
| Parameter | Value | Description |
|---|---|---|
| appid | string (required) | The application ID. See Application IDs for more information. |
| street | string | Street name. The number is optional. |
| city | string | City name. |
| state | string | The United States state. You can spell out the full state name or you can use the two-letter abbreviation. |
| zip | integer or | The five-digit zip code, or the five-digit code plus four-digit extension. If this location contradicts the city and state specified, the zip code will be used for determining the location and the city and state will be ignored. |
| location | free text | This free field lets users enter any of the following:
If location is specified, it will take priority over the individual fields in determining the location for the query. City, state and zip will be ignored. |
| output | string:xml(default),php | The format for the output. If php is requested, the results will be returned inSerialized PHP format. |
The schema document for this service response is located athttp://local.yahooapis.com/MapsService/V1/GeocodeResponse.xsd
| Field | Description |
|---|---|
| ResultSet | Contains all of the query responses. |
| Result | Contains each individual response. More than one result may be returned if the given address is ambiguous. Has attributes:
|
| Latitude | The latitude of the location. |
| Longitude | The longitude of the location. |
| Address | Street address of the result, if a specific location could be determined. |
| City | City in which the result is located. |
| State | State in which the result is located. |
| Zip | Zip code, if known. |
| Country | Country in which the result is located. |
The following is a sample response for the geocode of the Yahoo! headquarters:
The Geocoding service returns the standard errors.
The Geocoding service is limited to 5,000 queries per IP address per day. See information on rate limiting.
Use of the Yahoo! Maps APIs is governed by the Yahoo! Maps APIs Terms of Use and the Yahoo! Maps Terms of Use. These Terms of Use supplant the general Yahoo! Developer Network Terms of Use. See also the Usage Policy for more information about acceptable usage of these APIs or to request additional queries.
All Yahoo! Maps Web Services are discussed on the yws-maps mailing list.
YSlow analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Feature highlights:
» View YSlow Ruleset Limitations across several browsers/platforms.
Yahoo!'s Exceptional Performance team has identified 34 rules that affect web page performance. YSlow's web page analysis is based on the 23 of these 34 rules that are testable. Click each performance rule below to see the details.
» Check out the YSlow Ruleset Matrix to see how the grade is computed.
YSlow development is discussed in the Exceptional Performance group.
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.
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'YQL Insert/ Update/ Delete
You can use YQL to write and modify data on Web services and applications using SQL keywords: INSERT, UPDATE, and DELETE. These verbs let you manipulate data mapped onto an Open Data Table and enables developers to use Open Data Tables to do the following:
Open Data Table (ODT) developers can add support for these verbs into their tables by creating new binding types in their ODT definitions. They can then perform the insert/update/delete on the remote web service by creating an execute element that runs their JavaScript to create the right content payload and send it to the remote service. We've extended the capabilities in our server-side JavaScript, so y.rest() can now POST, PUT and DELETE.
Try creating a new Yahoo! update from the YQL console by following this link:
INSERT INTO social.updates (guid, title, description) VALUES (me, "Using YQL", "Try YQL, it's fun.");
Our goal is to make it easy for you to use YQL in the widest possible range of applications. Please read the notice and usage limits described below for more information. If you have additional questions, please read the YQL Terms of Service and/or contact us at the email address below.
Notice
Usage Limits
Additional Notes
Please send email to yql-questions [at] yahoo-inc.com with requests for additional information.
If you are a content or API provider and would like to learn how to opt out, or work better with YQL, please check our provider page.
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.
