The Gemini API provides you with the tools and resources you need to create, manage and retrieve advertiser data for your ads, ad groups and campaigns programmatically.
Developers are encouraged to take advantage of Gemini API as mobile traffic continues to increase rapidly, with the majority of ads on Yahoo mobile search inventory being served by Yahoo Gemini. Native advertising across Yahoo mobile inventory is only available through Yahoo Gemini.
The sooner you participate in Yahoo Gemini, the sooner the system can begin to build a performance history for your ad, so that your ad can earn better ranking and start getting you the clicks it deserves. As traffic ramps, your ad is then in the best position for cost-effective delivery and performance.
This documentation is intended for programmers who are developing apps to access Yahoo! content and search infrastructure. A prerequisite for working with Yahoo Gemini API is an understanding of HTTP, XML, JSON, and a cursory knowledge of query languages.
Once your users connect with Gemini OAuth, your application will be able to make API calls on their behalf without requiring additional authorization from them.
The workflow is as follows:
For information on how to set up your OAuth 2.0 client, refer to the OAuth 2.0 Guide. OAuth 2.0 is an updated version of the OAuth protocol that supersedes OAuth 1.0 and 1.0a.
Some key changes and distinctions from OAuth 1.0:
For detailed information on Yahoo!’s implementation of the OAuth standard, see the documentation OAuth Authorization Model on the Yahoo! Developer Network.
How often will the refresh token expire? Refresh tokens will not expire. They can only be invalidated explicitly by the user.
Should a Yahoo Partner always capture the refresh token in case it changes? As a best practice, you should always capture the refresh token after using it to get a new access token. It may change, and when it does you should use the new one.
What happens if you change your password? The existing refresh token should continue to work. A new refresh token will not be issued and you won’t need to request user consent and restart the OAuth flow. The existing refresh token should continue to work.
What scenarios require a Yahoo Partner to request user consent again? The scenario in which you explicitly revoke the OAuth access for your app on account info.
Yahoo Gemini provides you with a sandbox environment that you can use in your development workflow to test the creation and management of your advertising campaigns. You use the same consumer key and consumer secret you obtained when you set up your OAuth to access the sandbox.
The Gemini sandbox serves as a modified version of the production environment.
While all operations are designed to function the same in the sandbox as in the production environment, the campaigns and ads you create in this environment do not actually serve. The sandbox environment is completely separate from your production environment.
All campaigns, ads, and keywords you create in the sandbox are available in the sandbox environment only. There is no possibility that the ads you create in the sandbox will be accidentally served. Nor will your production accounts be charged for any mock transactions in the sandbox environment.
To better understand the relationships between the Gemini entities and data objects, you may wish to study this diagram. Please refer to Objects_ for more details on the different data objects and their attributes.
|Campaigns per advertiser account||10,000|
|Ad groups per campaign||10,000|
|Keywords per advertiser account||2,000,000|
|Keywords per ad group||10,000|
|Ads per ad group||50|
|Negative keywords per advertiser account||5,000|
|Location targeting objects per advertiser account||100,000|
|Maximum number of objects passed in API call||500|