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.

1

Get a token

Contact your Continu account team. Tokens are issued per organization. Store the token in a secret manager — never commit it to source control.
2

Pick an endpoint

For most warehouse use cases, start with POST /reports/content-completion/{from}/{until}.
3

Build a request body

The body is a field-selection document — set boolean flags for the fields you want returned, and provide filter objects to narrow results. See Request model for the full pattern.
4

Send it

POST it with your token in the Authorization header.

​
Example: first request

curl -X POST \
  'https://reports-latest.continu.co/api/v1/reports/content-completion/1714521600/1717200000' \
  -H 'Authorization: <your-token>' \
  -H 'Content-Type: application/json' \
  -d '{
    "email": true,
    "first_name": true,
    "last_name": true,
    "departments": true,
    "content": true,
    "assignment": true,
    "user_filter": {
      "departments": "5f8a1c2d4e6b7a9c0d1e2f3a"
    }
  }'
You’ll get back a JSON array, one record per matching completion, with the requested user fields populated and nested objects (content, assignment, etc.) included for any sub-objects you toggled on.
Prefer Postman? Download the pre-built collection with all 14 endpoints pre-populated with their available field flags.

​
Next

Authentication

Token format, lifetime, and rotation.

Request model

The field-selection pattern in depth.

Date handling

Unix epoch seconds, time zones, range targets.

Sync patterns

Incremental sync, backfills, handling deletes.