Ways to get data out

Who can do what

Reports contain end-customer personal data, so the whole Reports surface is limited to admins and editors; a viewer sees Your role cannot run reports.

• On-demand reports: admins and editors can request them. An admin sees, downloads and deletes every report in the workspace; an editor only the ones they requested (anyone else's answers 403 FORBIDDEN_REPORT_OWNER, whether or not it exists).
• Delivery reports mask recipients' email and phone for a non-admin requester, using the workspace's PII settings. Push tokens are never exported, for any role. The masking is decided when the report is built, by who requested it.
• Scheduled reports: admins and editors can list, create, edit, pause, enable and send them now; only admins can delete one.

API calls use a person's portal sign-in token (Authorization: Bearer …) and X-Tenant-Id; SDK, pk_, write and read keys don't open these routes. See Importing users and data: credentials.

On-demand reports

Downloads lists reports newest first, with Requested by, Requested, Completed, Rows and Status. Delete report removes the stored file.

Report types

• An open end date means today, and a date-only end includes that whole day.
• People, Custom and Delivery reports read at most 20,000 records.
• Delivery records are kept for 30 days, so a delivery report covers at most the last 30 days. A completed report's CSV is kept with the report, so it is the record of delivery history beyond that.

Reports API

export CF_API=https://api.contentflow.click/api/v1

# 1. Request a report (answers at once; status "queued")
curl -X POST $CF_API/reports \
  -H "Authorization: Bearer $CF_PORTAL_TOKEN" -H "X-Tenant-Id: $CF_WORKSPACE_ID" \
  -H 'Content-Type: application/json' \
  -d '{"type":"delivery","name":"SMS in September",
       "filters":{"dateFrom":"2026-09-01","dateTo":"2026-09-30","channel":"sms"}}'

# 2. Poll until "status":"completed" (or "failed")
curl $CF_API/reports/$REPORT_ID \
  -H "Authorization: Bearer $CF_PORTAL_TOKEN" -H "X-Tenant-Id: $CF_WORKSPACE_ID"

# 3. Download the CSV
curl -o report.csv $CF_API/reports/$REPORT_ID/download \
  -H "Authorization: Bearer $CF_PORTAL_TOKEN" -H "X-Tenant-Id: $CF_WORKSPACE_ID"

• GET /reports?page=&limit=&type=&status= lists reports: every report for an admin, your own for an editor.
• GET /reports/{id}/download answers the CSV itself (text/csv), not JSON. A report that isn't ready answers 409 with REPORT_DOWNLOAD_FAILED.
• DELETE /reports/{id} deletes it.
• Statuses: queued, processing, completed, failed (with error).

Scheduled reports

Reports → Scheduled → New report sets up an email that goes out on its own. Fields: Report name, Description (optional), Report type, Frequency (Daily, Weekly or Monthly), Day of week or Day of month (1 to 28), Send time (UTC), Recipients and Enabled.

• The email covers the last 24 hours for a daily report, the last 7 days for weekly and the last 30 days for monthly. Schedules are checked every hour.
• Older schedules can carry campaigns or engagement; they send the same email as Overview and are no longer offered.
• Up to 20 recipients per report and 10 scheduled reports per workspace.
• Send now builds and emails one copy straight away, even for a paused report. It can't be repeated within 5 minutes (Sent recently), and won't send while a send is running or when the last send never confirmed whether it was delivered (Last send did not confirm): check with the recipients before you send again.
• Pause and Enable switch the schedule; Edit and Delete (admin) change or remove it.
• With Test mode on, the dashboard won't enable a schedule or send one now, because the emails go to real recipients with live data.

Scheduled reports API

GET    /api/v1/settings/scheduled-reports                 list (admin, editor)
GET    /api/v1/settings/scheduled-reports/{id}            one
POST   /api/v1/settings/scheduled-reports                 create
PUT    /api/v1/settings/scheduled-reports/{id}            edit
PATCH  /api/v1/settings/scheduled-reports/{id}/toggle     { "enabled": false } pauses, true enables
POST   /api/v1/settings/scheduled-reports/{id}/send-now   email one copy now
DELETE /api/v1/settings/scheduled-reports/{id}            delete (admin)

POST body: { "name": "Weekly summary", "reportType": "overview", "frequency": "weekly",
             "dayOfWeek": 0, "hour": 9, "recipients": ["…"], "enabled": true }

• reportType defaults to overview; dayOfWeek (0 to 6) is required for weekly and dayOfMonth (1 to 28) for monthly; hour is UTC and defaults to 9.
• Validation failures answer 400 naming the field: an invalid email, more than 20 recipients, a missing day, or the 10-report limit.
• send-now answers 429 REPORT_SEND_COOLDOWN with Retry-After within 5 minutes of the last send, 409 REPORT_SEND_IN_PROGRESS or 409 REPORT_SEND_UNRESOLVED (don't retry: it may already have gone out), and 502 REPORT_SEND_FAILED when nothing was sent.

Analytics CSV

Export CSV in the Analytics page header downloads the dashboard you're looking at, for the selected range, as one CSV. It exports only the live rows that dashboard fetched and shows. When a view has nothing live to export, the button is off (Export is not available for this view yet).

Raw and compliance exports

On the Enterprise plan, two management API routes download the workspace's analytics data for a date range as a JSON file:

GET /api/v1/analytics/export/raw?startDate=2026-09-01&endDate=2026-09-30
GET /api/v1/analytics/export/compliance?startDate=…&endDate=…   adds exportedAt and the workspace id

On another plan they answer 403 with UPGRADE_REQUIRED. They are not in the dashboard.

Data Explorer

Audience → Data Explorer is for looking at your audience in the dashboard rather than exporting it. Overview shows the total of known profiles and how many have an email, a phone, a push token and marketing consent; Fields shows the distribution of any field; Correlate cross-tabulates two fields. It is not available in Test mode. To take the rows out, use a People or Custom report.

When it doesn't work

Next

• Analytics: where the numbers in analytics reports and dashboards come from.
• Importing users and data: the other direction, loading people and attributes in.