Yahoo! JAPAN Ads API v18 release

Updates

October 16, 2025: Updated due to the release of API v18
This update includes new information that differs from the initial announcement. Check the following release notes for details.

Yahoo! JAPAN Ads API Search Ads API v18
Yahoo! JAPAN Ads API Display Ads API v18

-----------------------------------------------------------

We will release a new version of Yahoo! JAPAN Ads API.

Product

  • Yahoo! JAPAN Ads Search Ads API
  • Yahoo! JAPAN Ads Display Ads API

Version released

v18

Schedule

October 15, 2025
*This date is subject to change.

Changes to the Search Ads API

Additional measures following the end of the autobidding type "Enhanced CPC"

We will take additional measures in response to the end of the autobidding type "Enhanced CPC."
Refer to the following announcement for details about the end of the feature.
Search Ads: End of autobidding type "Enhanced CPC"

Services

    • CampaignService
    • ReportDefinitionService

Change

・CampaignService
Remove the cpcBiddingScheme from CampaignService.

・ReportDefinitionService
The behavior of the ReportDefinitionService during add and getReportFields operations will be changed as follows. There are no changes to the interface. There are no changes in behavior in versions prior to v17.

■add

      • When reportType=BID_STRATEGY and fields[] includes BID_STRATEGY_TYPE, the following request will result in an error.
        • When language="JA" or null
          • filters[x].field=BID_STRATEGY_TYPE, and filters[x].values[] contains "Target Position on Search Results Page"
          • filters[x].field=BID_STRATEGY_TYPE and filters[x].values[] contains "Extended cost per click (formerly 'Maximize conversions')"
        • When language="EN"
          • filters[x].field=BID_STRATEGY_TYPE, and filters[x].values[] contains "Target position in search results"
          • filters[x].field=BID_STRATEGY_TYPE and contains filters[x].values[]"Enhanced CPC (Former:Maximize Conversions) "

■getReportFields

      • If reportType=CAMPAIGN is specified, fields[].fieldName won't return the following value.
         ENHANCED_CPC_ENABLED
      • If reportType=BID_STRATEGY is specified, fields[].fieldName won't return the following value.
         TARGET_SEARCH_PAGE_LOCATION
         BID_AUTOMATION
         BID_MULTIPLIER_OF_TARGET_PAGE_LOCATION
         LIMITED_BUDGETS
         LOW_QUALITY_KEYWORDS
         UPPER_BID_LIMIT_OF_TARGET_PAGE_LOCATION

Specifying radiuses will be available in geo targeting

In geo targeting, defining the target area by specifying a target point and its radius will be available.
*This feature is already available in the Campaign Management Tool. See the following for details.
Search Ads: Specifying radiuses will be available in geo targeting

CampaignTargetService

Change

Add a radius specification field to the CampaignTargetService (add/get/set/remove).
・Add radiusTarget under target
・Add RADIUS to targetType

Add errors in AbTestService

New error will be added. Add to all available versions.

Services

AbTestService

Change

Add the following to the errors returned by abTestService's abTest.errors[].
CAMPAIGN_CRITERION_OVER_LIMIT
Error details: You have reached the maximum total number of "Excluded keywords specified in the campaign," "Associations of target lists with campaigns," "Settings for geo targeting, day of week/hours targeting, and device targeting," and "Target pages of Dynamic Ads for Search (exclusions)."

Shopping Search Ads system renewal

We will renew the listing system for Shopping Search Ads of Search Ads (Shopping).
See the following announcement for details.
Search Ads (Shopping): System renewal and feature changes for Shopping Search Ads

Services

SsaReportDefinitionService

Change

    • getReportFields will return "SYSTEM_BRAND."
    • You can specify "SYSTEM_BRAND" when add.
    • After v18, the following fields are no longer available and will not be returned in getReportFields.
      CAMPAIGN_TRACKING_ID
      Field.ADGROUP_TRACKING_ID
      Field.PRODUCT_GROUP_TRACKING_ID

Changes to the Display Ads API

End of search keyword targeting

With the end of support for "Search keyword targeting," we will also end the creation and modification of search keyword lists. See the following announcement for details.
Display Ads (Auction): End of search keyword targeting and automatic migrations

Services

  • AdGroupTargetService
  • StatsService
  • RecommendationService
  • SearchKeywordIdeaService
  • SearchKeywordListService

Change

  • Remove targetType "SEARCH_TARGET" from AdGroupTargetService, StatsService.
  • Remove type "SEARCH_KEYWORD_LIST_IDEA" in RecommendationService.
  • Remove the endpoints of SearchKeywordIdeaService, SearchKeywordListService.

Fixed-position banner of Brand Panel for Smartphone

We will add a "fixed-position banner of Brand Panel for Smartphone." Refer to the following announcement in Japanese.
ディスプレイ広告(予約型)2025Q3 ブランドパネルトップカバー リリース 案内

Services

GuaranteedAdGroupAdService

Change

  • Add an enum for adTypes in GuaranteedAdGroupAdService/get.
    BRANDPANEL_TOPCOVER
  • Add a field under ad to indicate the fixed-position banner of Brand Panel for smartphones.
    brandPanelTopCover

IF change in reporting API

Change the specification when the report is retrieved and requires that the report be displayed in Japanese or English.

Services

ReportDefinitionService/getReportFields

Change

  • request
    Add the report item "lang." Specifying JA or EN is required.
  • response
    • Add the report item "displayFieldName."
    • End report items "displayFieldNameJa" and "displayFieldNameEn."

Maintenance

  • We will limit the number of offline conversions to 200 and end sorting, based on system load and sorting feature usage.
    • Services
      OfflineConversionService/get
    • Change
      Change OfflineConversionService/get as follows.
      • numberResults
        • default: 500 → 100
        • max: 1000 → 200
      • sorts
        • Because the service will end, specifying the sort it is no longer available, and it will be sorted by ID.
  • Review the error outside the BudgetOrderService budget setting range.
    The BudgetOrderService/set for search and display ads had differences in error codes that were outside the budgeted values. We will unify the error codes for both.
    • Services
      BudgetOrderService/set
    • Change
      Fix error code outside budget setting value from F0001 to V0001 when BudgetOrderService/set in display-ads-api.
      Applied to all available versions.
  • Add new services or add fields to existing services to support upcoming new bidding features.
    It won't be available until the official feature release. Details of the feature will be announced later.
    • Services
      • BiddingStrategyService
      • CampaignService
      • ReportDefinitionService
    • Change
      • Add a new BiddingStrategyService.
        • get
        • add
        • set
        • remove
      • CampaignService
        • request
          • get
            Add portfolioBiddingIds.
          • add, set
            Add biddingStrategyConfiguration/portfolioBiddingId.
        • response
          • Add biddingStrategyConfiguration/portfolioBiddingId.
          • Add biddingStrategyConfiguration/portfolioBiddingName.
      • ReportDefinitionService
        Add PORTFOLIO_BIDDING to the reportType.
  • Modify the field name of notTargetingProperAudienceList.
    • Services
      RecommendationService
    • Change
      Modify the field name createAdList[] in notTargetingProperAudienceList to adGroupList[].

Search Ads API and Display Ads API

In the Java client library, release versions with the suffix "*-spring5" will no longer be supported as of v17.

Comments

Find more details in the release notes and reference documents provided in the upcoming release.

End of Yahoo! JAPAN Ads API v16

Yahoo! JAPAN Ads API v16 will end with the following schedule:

  • Support end date: November 26, 2025
  • End of life date: Mid March 2026 (scheduled)
    *Wait for further announcements with detailed schedules.

Yahoo! JAPAN Ads API v15 will end with the following schedule:

  • End of life date: November 26, 2025
    *Support for this version has already ended.