Yahoo! JAPAN Ads API | Developer Center

日本語

Yahoo! JAPAN Ads Display Ads API v18 Release Note

Version released

v18

Date

October 15, 2025

Key points of this release

*Learn more about objects, etc., in the reference document.

1. Add portfolio bidding

We added portfolio bidding. Refer to the following announcement.
Display Ads (Auction): Adding portfolio bidding

Services

  • BiddingStrategyService
  • CampaignService
  • ReportDefinitionService

Change

  • Add 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.

2. End of search keyword targeting

With the end of support for "Search keyword targeting," we have stopped 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.

3. In-stream ads

We support "Yahoo! JAPAN Ads Display Ads (Auction) In-stream ads."
Refer to the following announcement.
Display Ads (Auction): Launch of in-stream ads

Services

  • AccountAuthorityService
  • CampaignService
  • AdGroupService
  • AdGroupAdService
  • AdGroupTargetService
  • StatsService

Change

  • Campaign delivery type: Add PRIVATE_MARKET_PLACE
    • AccountAuthorityService/get
      • Add to authorities return value
    • CampaignService/get,add
      • Add to campaignDeliveryType
        * You cannot create a campaign with PRIVATE_MARKET_PLACE.
        *The preceding two services are also returned for v15 to v17.
  • Device Type: Add CONNECTED_TV
    • Services
      • AdGroupService
      • AdGroupTargetService
      • StatsService
  • Ad Type: Add INSTREAM_AD
    • AdGroupAdService
      *You can't create in-stream ads.
  • Campaigns with a campaign delivery type PRIVATE_MARKET_PLACE, and ad groups and ads under it, cannot be created, edited, or apply targeting. You also cannot do the following for PRIVATE_MARKET_PLACE campaigns:
    • CampaignService/add,set
    • AdGroupService/add,set
    • AdGroupAdService/add,set
    • AdGroupTargetService/add,set,replace
  • Added report field values.
    • DEVICE：Connected TV
    • SPECIAL_PRODUCT_TYPE：Private market place
  • Added report field.
    • DEAL_TYPE: Product type

4. Add an audience range feature to the audience list (advanced segments)

We support the audience range feature for the audience list (advanced segments). Refer to the following announcement.
Add an audience range feature to the audience list (advanced segments)

Services

  • AudienceListService

Change

  • Add "audienceRange" to advancedSegmentsAudienceList in AudienceListService.
    • request
      • add, set
        • Add audienceRange to advancedSegmentsAudienceList
    • response
      • get, add, set, remove
        • Add audienceRange to advancedSegmentsAudienceList

5. Fixed-position banner of Brand Panel for Smartphone

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

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

6. 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."

7. Add SKAdNetwork items in various list views

We added features to SKAdNetwork. The values of the added report fields will be available after the launch date (October 29, 2025). Refer to the following announcement.
Add features to SKAdNetwork

Change

  • Add fields that can be specified for each report type.
    • App report
    • Audience list targeting report
    • Content keyword targeting
    • Placement targeting

8. Changes to placement list create and edit views

We support changes to the placement list, create and edit views. You can use this feature only after the release. Refer to the following announcement.
Changes to placement list create and edit views

Services

  • PlacementUrlIdeaService

Change

Add the following fields to the response when getting a placement URL list.

  • reaches: total reach across all devices
  • adRequests: total ad requests across all devices

9. Maintenance

  • We 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 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.
  • Modify the field name of notTargetingProperAudienceList.
    • Services
      RecommendationService
    • Change
      Modify the field name createAdList[] in notTargetingProperAudienceList to adGroupList[].
  • In the Java client library, release versions with the suffix "-spring5" will no longer be supported as of v17.

Differences between v17 and v18 IF

You can view the differences between Display Ads API v17 and v18 on this page, organized by IF.

End of Display Ads API v15

Display 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.

Display Ads API v15 will end with the following schedule:
End of life date: November 26, 2025
*Support for this version has already ended.

Developer Center

Related sites: