v2.2.12 2024-09-13 – Change Summary

An issue was corrected in /inventory/plans, where when a roadside plan query includes multiple media type groups, a reach percent goal and a single audience target geography, the calculated plan reach percent was sometimes be over-estimated (indicating a fewer number of spots satisfies the plan goal than is correct).
An issue was corrected in /inventory/plans, where multiple audience target geographies and multiple media type groups will return a 500 error if one of the media type groups returns no spots matching the media type group criteria.
An issue was corrected in /inventory/plans, where the endpoint did not default to Persons 0+ (i.e., 9330), when a target segment was omitted from the query and instead returned a 500 error.

v2.2.11 2024-07-16 – Change Summary

As of 6/28/24, an issue was corrected where /inventory/search results could not be returned on some pages when the page_size value (i.e. number of spots per page of results) was set to 1000 or greater
An issue was corrected where queries sent to the inventory/search/named endpoint would not succeed if the count of spots that matched the dimensional inputs was greater than 1000
An issue was corrected where queries sent to the inventory/search endpoint would not succeed if the volume of unique spot IDs used as input parameters was greater than 1425
An issue was corrected where certain queries sent to the inventory/search/named endpoint would not succeed if the 2023 dataset was used
An issue was corrected where certain queries sent to the inventory/plans endpoint would not use all spots in the market to fulfill the stated spot count goal
An issue was corrected where certain queries sent to the inventory/plans endpoint would not allow users to input a specific count of spots above a certain threshold

As of 5/7/24, an issue was corrected where /inventory/measures/summary gave a slightly an incorrect target in-market population when measures for two or more spots was requested.
As of 5/27/24, the ‘Current’ annual forecast for 2024 (known as ‘product_name’=20240301) became the default data product served via the API.
An issue was corrected where /inventory/search/summary did not return the correct reach & frequency when the number of max_frames was greater than one (which impacts scheduled fleet spots as well as some place-based fleet spots).
An issue was corrected where /inventory/plans did not calculate reach & frequency correctly in some scenarios, depending on the target_geography_list and/or inventory_market_list and number of spots inputs used in the API request.

...

...