Yahoo! JAPAN Ads API | Developer Center

日本語

Yahoo! JAPAN Ads Display Ads API v17 Release Note

Version released

v17

Date

June 30, 2025

Key points of this release

1. 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. Learn more in the following announcement.
End of search keyword targeting

Services

  • SearchKeywordListService/add, set

Changes

  • Removed add and set from the SearchKeywordListService endpoint.

2. Adding URL to the audience list "Advanced segments"

You can specify a URL in the "Advanced segments" of the audience list. Additionally, you can get the user size for the specified URL using the EstimatedUserSizeService.
*This feature is already available in the Campaign Management Tool. Learn more in the following announcement.
Adding URL to the audience list "Advanced segments"

Services

  • AudienceListService
  • EstimatedUserSizeService

Changes

  • Added "urls[]" to advancedSegmentsAudienceList in AudienceListService.
  • Added "urls[]" to the selector in EstimatedUserSizeService.

3. Adding features for the campaign goal "Gain friends" ads

We support adding "Carousel" ads for the campaign goal "Gain friends." Additionally, we support the addition of settings for "Responsive (image/video)."
*This feature is already available in the Campaign Management Tool. Learn more in the following announcement.
Adding features for the campaign goal "Gain friends" ads

Services

  • AdGroupAdService/get,add,set

Changes

  • get
    • You can get carouselGainFriendsAd.
    • You can get the viewing beacon URL with responsiveGainFriendsAd.
  • add
    • You can add carouselGainFriendsAd.
    • You can add the viewing beacon URL with responsiveGainFriendsAd.
    • When the adType is RESPONSIVE_GAIN_FRIENDS_AD, you can specify the following:
      Third-party script tag src attribute URL
      Viewable impression beacon URL
  • set
    • You can modify carouselGainFriendsAd.
    • You can modify the viewing beacon URL with responsiveGainFriendsAd.

4. End of site category targeting

With the end of support for "Site category targeting," we removed the relevant items. Site category targeting is no longer available. Learn more in the following announcement.
End of site category targeting

Services

  • AdGroupTargetService/get,add,set,replace,remove
  • StatsService/get
  • ReportDefinitionService/getReportFields
  • PlacementUrlIdeaService/get
  • DictionaryService/getSiteCategory

Changes

  • In AdGroupTargetService/get, add, set, replace, remove, made the following changes:
    • Removed "SITE_CATEGORY" from targetType.
    • Removed "siteCategoryTarget" from Request and Response.
  • In StatsService/get, made the following changes:
    • Removed "SITE_CATEGORY" from targetType.
    • Removed "siteCategoryTarget" from Request and Response.
  • Removed "SITE_CATEGORY" from reportType in ReportDefinitionService/getReportFields.
  • In PlacementUrlIdeaService/get, made the following changes:
    • Removed "siteCategories[]" from Request.
    • Removed "siteCategory[]" from Response.
  • Removed "getSiteCategory" from the endpoints of DictionaryService.

5. Specification change for download files of Dynamic Ads for Display

We support the specification change for files downloaded in Dynamic Ads for Display.
*This feature is already available in the Campaign Management Tool. Learn more in the following announcement.
Emoji addition and file management specification changes

Services

  • FeedService/downloadDisApprovalReasonList
  • FeedDataService/downloadErrorFile

Changes

  • In FeedService/downloadDisApprovalReasonList, you can specify "SJIS" for encoding.
  • You can specify encoding in FeedDataService/downloadErrorFile.

6. Launch of the tracking tag and new conversion API

We support for the tracking tag and the new Conversion API. See the following announcement for details.
Launch of the tracking tag and new conversion API

Services

  • AudienceListService
  • ConversionTrackerService

Changes

  • In StatsService/get, made the following changes:
    • Added null to the response's retargetingTagId.
    • You can specify or return ruleType=EVENT_TYPE when audienceListType=WEBSITE_VISITORS.
    • Removed customAudienceId.
    • In add/set/remove, specifying retargetingTagId became optional.
  • In ConversionTrackerService
    • Added "LY_TAG_CONVERSION" to the conversionTrackerType enum.
    • Added a new field, lyTagConversion, under conversionTracker.

7. Maintenance

  • We modified the "limitValue" field in FeedService/get to int64 (long type).
  • You can't create reports specifying an MCC account. If you specify an MCC account or root MCC in ReportDefinitionService, error code 0097 is returned.
  • We modified the errors in the following fields of CampaignService. skanOptimaizeAdDeliveryEnabled → skanOptimizeAdDeliveryEnabled
  • In the Java client library, release versions with the suffix "-spring5" will no longer be supported as of v17.
  • For future feature additions, we have added "CampaignGoalSubType" to CampaignService. You can use the features only after the release. We will make an announcement once details have been decided.
  • For future feature additions, we have added items to the following web services. You can use the features only after the release. We will make an announcement once details have been decided.
    AccountService, AccountManagementService, BudgetOrderService, RecommendationService
  • The error code for the following cases has been changed from "F0001" to "V0001." All available versions
    • CampaignService Error for cases where BiddingStrategyType is "MAXIMIZE_CONVERSION_VALUE" and targetRoas has more than two decimal places (e.g., 10.001 or 20.0002)
    • AdGroupService Error for cases where campaignBiddingStrategyType is "MAXIMIZE_CONVERSION_VALUE" and targetRoas has more than two decimal places (e.g., 10.001 or 20.0002)
  • In VideoService/download, the "qualityType" Nullable setting has been changed from true to false.

Differences between v16 and v17 IF

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

End of Display Ads API v15

Display Ads API v15 will end with the following schedule:
Support end date: July 28, 2025
End of life date: Early of November 2025 (scheduled)
*Wait for further announcements with detailed schedules.

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

Developer Center

Related sites: