Product Bulletin

Welcome to the Yahoo Gemini API Product Bulletin. This update includes a quick snapshot of recent and upcoming releases and is focused on features supported by the API. A summary of supported functionality is also included.

Product Bulletins are updated on a monthly cadence for Gemini API partners, account managers and developers.

September, 2016

New Expanded Text Ad Titles Introduced

  • Yahoo Gemini now provides support for Expanded Text Ads for Gemini Search campaigns. If you’re a search advertiser, you’ll have additional space now in the Gemini UI to craft longer and more compelling ad titles for improved user engagement.

  • For more details on the new features available to Gemini advertisers, see What’s New, Expanded Text Ads FAQs, Bulk Object Type Ad, Gemini Account Sync, and Dimensions. In Dimensions for the Ad object, the string Ad Title 2 attribute is now available as a second line title of the ad shown to users, with a 30-character text limit (both Ad Title and Ad Title 2 can include 30 characters of text).

New Gemini API Video Tutorials

New Cube Name For Close of Books Added

  • cubeName field added to Close of Books, enabling you to query the name of the cube for COB. The field is optional; you can only pass in one cube name at a time. To query whether books are closed for a given date, you make a GET call to{advertiserId}&date={date}&cubeName={cube_name}

and pass in these parameters: advertiserID, date and cubeName.

For more information, refer to About Books Closed.

Call to Action Buttons

  • All Call to Action values may now be set to any campaign objective. Adding call to action buttons to your native ads encourages users to take specific actions after seeing your ad. A call to action value can be set using the callToActionText field in the Ad object.

  • For a complete list of values, see Call to Action Buttons.

Reminder: Gemini v2 API Resources and v1 Deprecation Timeline

  • New Gemini v2 API has been released. Starting on June 1, 2016, Yahoo Gemini migrated the programmatic Gemini API from v1 to v2; the current version of the Gemini API is v2. Be sure to read the sections on Versioning and API v1 Deprecation, plus the FAQs for details.


The Gemini v1 API will be supported for 90 days beyond the June 1, 2016 deprecation date. After that date, starting on September 1, 2016, the Gemini v1 API will be available for one year. After that time, it will be relegated to End of Life (EOL) status.

  • See the What’s New section for more information about the new Gemini v2 API.

Update: Deprecated Reporting Endpoint

  • Update: Please be aware that action may be required for the following deprecated reporting endpoint.

  • If you currently make calls only to /v2/rest/reports/custom for both POST and GET, there is no action required.

  • If you currently make POST calls to /v1/rest/reports then you need to migrate to the /v2/rest/reports/custom endpoint ASAP.

  • If you currently make POST calls to /v1/rest/reports/custom and GET calls to /v1/rest/reports, then you need to migrate to v2 before v1 EOL NEXT year Sept 1, 2017.

  • Please see documentation for the new reporting endpoint for more information.

  • For additional reference, please see Gemini API documentation: Navigating the API and Reporting.

Getting Started Guide: OAuth 2.0 Authentication Steps

New Glossary of Gemini Terms

Check Out What’s New

  • To stay current with changes, updates and new features in the v2 Gemini API, you’ll want to read this section. What’s New is updated on a weekly cadence for Gemini API partners and developers. Resources includes a link to archived Gemini Release Notes.

Using the Gemini Sandbox Environment

  • The Gemini API lets you work with a sandbox environment to test campaigns you’ve created and managed. You use the same consumer key and consumer secret you obtained when you set up your OAuth to access the sandbox.

Resource URI{resource}
  • 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.

  • You will need to create a sandbox account in order to test in this environment. You can do this by making a POST call to the sandbox signup endpoint and passing in the name you wish to call your test advertiser. The response will be a test advertiser object that will only be available in the sandbox environment. For more details, see Testing - Sandbox.

  • Be sure to check out the new video tutorial describing How to set up your Sandbox Environment in the Programmatic Gemini API - Episode 3.

Required Fields by Ad Type Matrix

  • We’ve added a new matrix which details the required fields when serving different ad types. For more information, see Ad documentation > Matrix view of required fields.