Overview

Retrieve the latest date for which processed performance reporting data is available for an advertiser.

Use this endpoint before creating Performance Snapshot reports to confirm data availability, validate reporting date ranges, and automate daily reporting pipelines.

Availability

Supported for Onsite Display and Offsite Display (Walmart DSP) reporting workflows.

How it works

Performance reporting data is refreshed once daily and is typically available through T-1, subject to processing completion.

The Latest Report Date API returns the most recent processed reporting date for an advertiser. Use this date to determine the latest reporting period available before creating a Performance Snapshot.

Before you begin

• Valid advertiserId
• Reporting read access for the advertiser account

Endpoint

GET /api/v1/latestReportDate

View technical specifications

Request details

How this request is used

Use this endpoint to determine the latest processed reporting date before requesting historical performance data.

The endpoint supports scheduled reporting workflows by helping partners avoid requesting dates that have not completed processing.

Key fields and behaviors

Important behavior

• The endpoint returns data availability for the specified advertiser.
• Performance reporting is refreshed daily and typically available through T-1.
• The latest available date may be earlier than T-1 if processing has not completed.
• The endpoint does not generate a report or return performance metrics.

Sample request

curl -X GET \ 'https://developer.api.us.stg.walmart.com/api-proxy/service/display/api/v1/api/v1/latestReportDate?advertiserId=600001' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer <auth_token>' \ --header 'WM_SEC.AUTH_SIGNATURE: <auth_signature>' \ --header 'WM_SEC.KEY_VERSION: 1' \ --header 'WM_CONSUMER.ID: <consumer_id>' \ --header 'WM_CONSUMER.intimestamp: <timestamp>'

Response details

What this response returns

The response identifies the most recent processed performance reporting date available for the advertiser.

Key fields to use

• latestReportDate
  Most recent data for which performance reporting data has completed processing and is available.

How to interpret the response

Use latestReportDate as the upper boundary when creating Performance Snapshot requests.

For example, if the current date is July 17 and the response returns 2026-07-16, performance reporting data is available through July 16.

If the returned date is earlier, use the actual returned date rather than assuming T-1 data is ready.

Sample response

{ "advertiserId": "600001", "latestReportDate": "2023-08-13"
}

Using the latest report date in automated reporting

For scheduled reporting pipelines, retrieve latestReportDate before generating daily or historical performance reports.

1. Call GET /api/v1/latestReportDate for the advertiser.
2. Compare the returned date with the reporting period your pipeline needs.
3. Set the Performance Snapshot endDate to a date no later than latestReportDate.
4. Create the Performance Snapshot using the validated date range.

Common issues

• Assuming the latest available reporting date is always yesterday
• Requesting a Performance Snapshot with an endDate later than latestReportDate
• Hardcoding reporting dates without checking availability
• Using an invalid advertiserId or lacking reporting access
• Expecting this endpoint to return performance metrics or generate reports

What happens next

Use the returned latestReportDate to validate the reporting period and create a Performance Snapshot.

For the asynchronous snapshot generation, retrieval, and download workflow, see Snapshot Reporting.

Related pages

• Reporting API Overview
• Snapshot Reporting
• Create Performance Snapshot
• Retrieve Snapshots
• Dimensions and Metrics