Skip to main content

Documentation Index

Fetch the complete documentation index at: https://reporting.continu.com/llms.txt

Use this file to discover all available pages before exploring further.

All date range parameters in the URL path are Unix epoch seconds in UTC, not ISO 8601 strings. 
/reports/content-completion/1714521600/1717200000
                            ^from       ^until
from is inclusive, until is exclusive. To pull data for the month of May 2024 UTC, use from=1714521600 (May 1 00:00:00 UTC) and until=1717200000 (June 1 00:00:00 UTC).

​
Generating epoch values

from datetime import datetime, timezone

from_ts = int(datetime(2024, 5, 1, tzinfo=timezone.utc).timestamp())
until_ts = int(datetime(2024, 6, 1, tzinfo=timezone.utc).timestamp())

​
Response timestamps

Timestamps in response bodies are returned as ISO 8601 strings in UTC, not epoch seconds. Example: 
{
  "completed_on": "2024-05-15T14:32:00Z",
  "createdAt": "2024-05-15T14:32:01Z"
}

​
Which date field does the path range apply to?

Some endpoints support multiple semantic date fields (e.g., assignment endpoints have assigned_date, completed_date, due_date). Use the range_target body field to specify which one the {from}/{until} path range should filter on: 
{
  "range_target": "completed_date",
  "user_filter": { "departments": "..." }
}
If range_target is omitted, each endpoint applies a sensible default (typically completed_date or created_at).
When building incremental syncs against assignment-style endpoints, set range_target to updated_date so any change to an assignment — completion, reassignment, cancellation — pulls the record back in your next sync.