Prepare and reuse a stored GA4 report through the regular async worker

Requires analytics:read and site access. Accepts the same parameters as GET in a JSON object or in the query string, exclusively. source must be stored. Existing fresh reports return immediately; missing reports reuse or enqueue collection. Repeat GET with the same dates after completion. This does not change scheduled collection or backfill.

More context and worked examples are in the developer guide.

Example request

curl --fail-with-body --request POST \
  'https://satelliteai.io/api/v1/sites/123/ga4/reports/sessions_over_time' \
  -H 'Content-Type: application/json' \
  --data '{"start_date":"2026-01-01","end_date":"2026-10-25","limit":100}' \
  -H "Authorization: Bearer $SATELLITE_API_KEY"

Replace the example IDs with values returned by the discovery endpoints. Example values are placeholders, not real records.

Parameters

Unknown or repeated query parameters return 400.

JSON request body

Send Content-Type: application/json. The request body is optional. Fields below describe the request; response fields follow separately.

Data dictionary

Stored report ready, or partial daily data with coverage metadata. Stored reports come from the canonical GA4 store. Missing intervals return a pending object; available reports can have an empty rows array. Use report_set_id to pin exact-range pages. Daily history and live Google results can change during pagination.

202: Collection pending. Response uses Ga4Report and Ga4Meta, including report_metadata.collection.jobs when work is queued.

[] marks an array element. nullable means the value can be null; treat it as unknown, not zero. always present means the key is always included in the object.

Response metadata

Error responses

Errors return {"error": {"code", "message", "request_id"}}. See error handling for retry guidance.