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.

July, 2017

Introducing Gemini V3 API and Upgraded URLs (UUs)

The new Gemini v3 API has been released as of July 25, 2017. This release provides partners and developers with the following features and capabilities:

  • Support for Upgraded URLs (UUs), which enable you to better define and control the landing page and tracking of your URLs. For more information on Upgraded URLs (UUs) in the new Gemini v3 API, refer to Upgraded URLs. Note the Migration Path and Upgrade Account to Work as UU sections.
  • Greater API object stability, as well as improved management of API changes, building on the enhancements in the Gemini v2 API.
  • Support for Site X Device Targeting with new available targeting attributes. For more information about Site X Device Targeting, refer to v3 Site X Device Targeting. Note that Bid by Site Adjustments are now available in the Gemini UI. For more information, refer to Use Site Bid Adjustments To Modify Your Bids in the Gemini Advertiser Guide.
  • Additional bug and error fixes for improved performance and stability.
  • See the What’s New section and Navigating the API for more information about the new Gemini v3 API. Developers are encouraged to migrate to the v3 Gemini API in order to maintain access to the latest features and functionality. Please note that new features are only added to the current version. For reference, see details on v2 Objects.

Reminder: v1 API Deprecation

  • Reminder: The Gemini v1 API was deprecated on June 1, 2016. Starting on September 1, 2017, the Gemini v1 API will be relegated to End of Life (EOL) status. In addition, new features will not be added to v1.

Reminder: Deprecated v1 Reporting Endpoint

  • Please be aware that action may be required for the following deprecated reporting endpoint.
Old: https://api.gemini.yahoo.com/v1/rest/reports
New: https://api.gemini.yahoo.com/v2/rest/reports/custom
  • 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 THIS year Sept 1, 2017.

Gemini Native Ads Specs and Resources

Gemini API Video Tutorials

Getting Started Guide: OAuth 2.0 Authentication Steps

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

https://sandbox-api.gemini.yahoo.com/v2/rest/{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 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.