LY Ads API | Developer Center

日本語

2026/02/26

Yahoo! JAPAN Ads API v19 release

Updates

February 26, 2026: Updated due to the release of Yahoo! JAPAN Ads API v19
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 v19
Yahoo! JAPAN Ads API Display Ads API v19
-----------------------------------------------------------

Products

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

Version Released

v19

Schedule

February 25, 2026
*This date is subject to change.

Changes to the Search Ads API

Add age and gender targeting and rename target lists

We will add targeting by age and gender.
We will rename "Target list" to "Audience list" in Search Ads.
See the following for details.
Search Ads: Add an age and gender targeting feature and rename target lists

Services

Rename target lists:

  • AudienceListService (previously RetargetingListService)
  • AdGroupAudienceListService (previously AdGroupRetargetingListService)
  • CampaignAudienceListService (previously CampaignRetargetingListService)
  • ReportDefinitionService
  • AuditlogService
  • AbTestService
  • AdGroupService
  • CampaignService

Age and gender targeting:

  • AudienceListService (previously RetargetingListService)
  • AdGroupAudienceListService (previously AdGroupRetargetingListService)
  • CampaignAudienceListService (previously CampaignRetargetingListService)
  • ReportDefinitionService

Change

Rename target lists:

  • We will rename the following services (the following descriptions use the new names):
    • "RetargetingListService" → "AudienceListService"
    • "AdGroupRetargetingListService" → "AdGroupAudienceListService"
    • "CampaignRetargetingListService" → "CampaignAudienceListService"
  • We will change terms such as "Target list" and "Retargeting list" to "Audience list." The changes by version are as follows.
    • v19: service names, column names, error messages, references, and more
    • v18 and earlier: error messages and references
  • In ReportDefinitionService, we will add Enums with updated names and definitions for audience lists. The existing Enums are scheduled to be discontinued in a future version.
    • Add: "CAMPAIGN_AUDIENCE_LIST"and "ADGROUP_AUDIENCE_LIST"
    • Scheduled for removal (can be used in parallel with the Enums that will be added in v19): "CAMPAIGN_TARGET_LIST" and "ADGROUP_TARGET_LIST"
  • We will update entity types in AuditlogService as follows:
    • "NEGATIVE_CAMPAIGN_USER_LIST" → "NEGATIVE_CAMPAIGN_AUDIENCE_LIST"
    • "NEGATIVE_AD_GROUP_USER_LIST" → "NEGATIVE_AD_GROUP_AUDIENCE_LIST"
    • "AD_GROUP_USER_LIST" → "AD_GROUP_AUDIENCE_LIST"
    • "TARGET_LIST" → "AUDIENCE_LIST"

Age and gender targeting:

*This feature is available for some users. If the feature is not available to a user, AudienceListService/getDemographic returns an empty response. The detailed offering conditions are not disclosed.

  • AudienceListService/getDemographic:
    You can select audience lists (previously target lists) by age and gender.
  • AdGroupAudienceListService/get, add, set:
    We will add a flag under criterionUserList to indicate whether the audience list (previously target list) is for a specific age or gender.
  • CampaignAudienceListService/add:
    When you try to add age- or gender-based audience lists (previously target lists), "Invalid value" is returned.
  • ReportDefinitionService/get, add, remove, getReportFields:
    You can specify "Target audience" (field name: TARGET_ALL).

Add business name assets

We will add new "Business name asset" to ad display assets.
See the following for details.
Search Ads: Adding Business name assets

Services

  • AccountAssetService (new)
  • AssetService
  • CampaignAssetService
  • ReportDefinitionService
  • CampaignExportService
  • AuditLogService

Change

  • Add the new web service "AccountAssetService."
  • AssetService/get, add, set, remove:
    Add "BUSINESS_NAME" to assetData/type.
  • CampaignAssetService/get, replace, set:
    Add "BUSINESS_NAME" to type.
  • ReportDefinitionService/get, add, remove:
    Add "ACCOUNT_ASSET" to reportType.
  • CampaignExportService/add:
    Add "BUSINESS_NAME_ASSET" to entityTypes.
  • AuditLogService/get, add:
    Add "ACCOUNT_ASSET" to entityType.

Add a new report metric "Click share"

We will add a new report metric "Click share."
See the following for details.
Search Ads: Adding new report metric "Click share"

Services

  • ReportDefinitionService

Change

  • ReportDefinitionService/get, add, remove, getReportFields:
    You can specify "Click share" (field name: SEARCH_CLICK_SHARE).

Changes to the Display Ads API

Changes due to expanded tracking tag availability

With tracking tag issuance and management in Business Manager and support for LINE official accounts, we will make the following changes.
See the following announcement for details.
Display Ads: Impact of expanding the availability of tracking tags

Services

  • TrackingTagService
  • AudienceListService
  • ConversionTrackerService

Change

  • Add a new service "TrackingTagService" (get) to get tracking tags.
  • AudienceListService:
    Add trackingTagId to the websiteVisitorsAudienceList that will be used in get, add, set, and remove.
  • ConversionTrackerService
    • Change conversionTrackerTypes from LY_TAG_CONVERSION to TRACKING_TAG_CONVERSION.
    • Rename lyTagConversion to trackingTagConversion.
    • Add trackingTagId to trackingTagConversion (previously TagConversion).

Optional logo image setting for carousel ads

We will update carousel ads to make logo image settings optional.
See the following announcement for details.
Display Ads: Logo image for carousel ads becomes optional

Services

  • AdGroupAdService

Change

  • Add "isRemoveLogoMediaId" to AdGroupAdService to remove logo images.

Partial changes to the placement list create/edit view (from v18)

From v18, we supported partial changes to the placement list create/edit view.
This is a reminder about the feature that became available in v18 as of December 17, 2025. Refer to the following announcement.
Display Ads (Auction): Changes to placement list create and edit views

Services

  • PlacementUrlIdeaService

Change

  • Add the following fields to responses when getting placement URL candidates:
    • reaches: total reach across all devices
    • adRequests:
      Total ad requests across all devices
  • The following fields are scheduled for removal on April 1, 2026. Use the preceding new field instead.
    • desktopReaches: reach per PC
    • desktopAdRequests: ad requests per PC
    • smartPhoneReaches: reach per smartphone
    • smartPhoneAdRequests: ad requests per smartphone
    • tabletReaches: reach per tablet
    • tabletAdRequests: ad requests per tablet

Maintenance

  • StatsService: image and video statistics will no longer be available. Based on your usage status, the "Performance data check feature for the image and video list view," which has been discontinued in the Campaign Management Tool, will also no longer be available in the Yahoo! JAPAN Ads API.
    *This change applies to all supported versions, including v19.
    • Services
      StatsService/get
    • Change
      Remove the following items from type.
      IMAGE
      VIDEO
  • AudienceListService/get: add an option to get detailed settings.
    • Services
      AudienceListService/get
    • Change
      Add a flag called includeDetail to get details. By setting this flag to "True," you can get the detailed settings.
  • ConversionTrackerService: add "Generate leads" as a conversion tracking purpose.
    • Services
      ConversionTrackerService/get, add, set
    • Change
      We will add "GENERATE_LEADS" (Generate leads) to category in ConversionTrackerService/get, add, and set.

Comments

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

End of Yahoo! JAPAN Ads API v17

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

  • Support end date: March 17, 2026
  • End of life date: July 28, 2026

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

  • End of life date: March 17, 2026
  • *Support for this version has already ended.

Developer Center

Related sites: