Get Latest Report Date V2

Check the latest available report date by report type.

⚠️

Important: Use V2 for new integrations. Partners using V1 should begin migrating to V2, as V1 will be deprecated in a future release cycle.

Overview

Before submitting a snapshot job, you can retrieve the latest available report date for a given report type via GET /api/v2/latestReportDate. This returns the most recent day for which Snapshot v2 reports can be generated.

After confirming the date is available for your report type, create a Snapshot v2 report request for the provided date and retrieve the report. This step ensures you request reports only for dates with refreshed data.

📘

URL: GET /api/v2/latestReportDate

Query Parameters

No specific request parameters are required to retrieve the latest report date.

Response

ElementDescriptionType
reportTypeThe report type associated with the returned report date. See supported report types section for possible values.string
latestReportDateThe latest date for which data is available for the report type.

Format: yyyy-MM-dd
date

Sample Response

The response is an array. Each object represents the latest available report date for one report type.

 [ { "reportType": "keyword", "latestReportDate": "2026-02-25" }, { "reportType": "adItem", "latestReportDate": "2026-02-25" }, { "reportType": "adGroup", "latestReportDate": "2026-02-24" }, { "reportType": "itemRecommendations", "latestReportDate": "2026-02-21" }
]

Supported Report Types

Use latestReportDate for the specific reportType required by your integration. Each report type may have its own latestReportDate. Not all report types may be available for the same date.

Report TypeSubmit viaCadence
adItemPOST /api/v2/snapshot/reportdaily
adGroupPOST /api/v2/snapshot/reportdaily
attributedPurchasesPOST /api/v2/snapshot/reportdaily
brandPOST /api/v2/snapshot/reportdaily
categoryPOST /api/v2/snapshot/reportdaily
itemHealthPOST /api/v2/snapshot/reportdaily
itemKeywordPOST /api/v2/snapshot/reportdaily
keywordPOST /api/v2/snapshot/reportdaily
pageTypePOST /api/v2/snapshot/reportdaily
placementPOST /api/v2/snapshot/reportdaily
platformPOST /api/v2/snapshot/reportdaily
searchImpressionPOST /api/v2/snapshot/reportdaily
videoCampaignsPOST /api/v2/snapshot/reportdaily
videoKeywordsPOST /api/v2/snapshot/reportdaily
keywordRecommendationsPOST /api/v1/snapshot/recommendationsdaily
matchTypeKeywordRecommendationsPOST /api/v1/snapshot/recommendationsdaily
outOfBudgetPOST /api/v2/snapshot/recommendationsdaily
searchTrendsGET /api/v1/insightdaily
advancedInsightsPOST /api/v1/snapshot/insightdaily
itemAlertsPOST /api/v2/snapshot/recommendationsdaily
itemRecommendationsPOST /api/v1/snapshot/recommendationsweekly

Best Practice

📌

Do not use this endpoint to retrieve report data. Use it only to verify availability before submitting a snapshot request.

  1. Call this endpoint once after 10 AM PT and use the response as a readiness check.
  2. Submit a snapshot request only when latestReportDate returns the date you want to pull the data for the relevant report type.
  3. If the latest date that you want to pull the data for is not returned, retry no more than once per hour until the current report date is available. Avoid calling this endpoint more frequently than needed; it is intended for availability validation, not data retrieval.

Note: itemRecommendations updates weekly, so its latestReportDate may not advance daily.

Upgrade from V1 to V2

GET /api/v1/latestReportDate remains supported and continues to function as-is. However, partners are encouraged to migrate to GET /api/v2/latestReportDate to use report-level availability.

V1 returns a single global latest report date, while V2 returns the latest available report date for each report type, allowing integrations to determine availability for the specific reports they request.

Upgrade Checklist

  1. Replace GET /api/v1/latestReportDate with GET /api/v2/latestReportDate in your scheduling or orchestration logic.
  2. Update your response parsing to handle an array response instead of a single object.
  3. Read the reportType and latestReportDate values from each array item.
  4. Filter the response for the reportType values required by your integration.
  5. For itemRecommendations, add special handling: its latestReportDate advances weekly, not daily.
  6. Run both endpoints in parallel during your transition period to validate your v2 parsing before retiring the v1 call.


What’s Next

Use the returned latestReportDate for the relevant reportType when submitting a snapshot job.

Did this page help you?