Reporting & Data Extraction

Overview

This is the reference for extracting operational data from Xenia into dashboards and BI tools (Power BI, Looker Studio, custom warehouses). Everything here is reachable with a client key and falls into four groups:

Submission records & counts — raw submission (checklist log) data and status breakdowns
Task analytics — pre-aggregated task/compliance metrics (counts, trends, on-time rates)
Submission exports — Excel/PDF/spreadsheet generation
Grid reports & scheduled reports — saved report definitions, spreadsheet exports, and automated delivery

Authentication & base URL

Base URL is https://api.xenia.team; every path starts with /api/v1. Authenticate with your client credentials (see Client Key Setup):

x-client-key: <your-client-key>
x-client-secret: <your-client-secret>
x-client-user: <optional-user-id>

The workspace is derived from the key — you don’t send a workspace-id header. Where a path contains {workspaceId} it must be your key’s own workspace; the ops reporting endpoints also accept an unscoped form (/api/v1/ops/...) and resolve the workspace from the key automatically. Each route enforces the key’s default-user permission — task analytics and grid / scheduled-report reads require CAN_VIEW_REPORTING (grid / scheduled-report writes require CAN_MANAGE_DASHBOARDS), while submission records and counts are instead scoped to the key user’s authorized locations (no CAN_VIEW_REPORTING gate).

Responses use Xenia’s standard envelope: a data payload plus a meta object. There is no status, statusCode, success, or requestId field, and successful POST calls return HTTP 200 (report-schedule creation returns 201; PDF generation returns 202). Analytics/report meta is typically empty ({}) — the payload and any pagination live under data. Requests are bounded by an ALB timeout of roughly 60 seconds, so filter and paginate aggressively.

Submission Records

Raw submission (checklist log) records — the backbone of most BI pulls. All fields are optional; always set an explicit limit (the default is enormous). Endpoint: POST /api/v1/ops/template-submissions

curl -X POST "https://api.xenia.team/api/v1/ops/template-submissions" \
  -H "x-client-key: YOUR_CLIENT_KEY" \
  -H "x-client-secret: YOUR_CLIENT_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "fromDate": "2024-12-01",
    "toDate": "2024-12-31",
    "checklists": ["template-uuid"],
    "statuses": ["submitted", "Approved"],
    "locations": ["location-uuid"],
    "offset": 0,
    "limit": 500,
    "includeItems": false
  }'

Request Body (all optional):

Field	Type	Default	Description
`fromDate` / `toDate`	string	—	Date range (applied only when both are valid)
`checklists`	string[]	—	Filter by template (ChecklistId)
`statuses`	string[]	—	Filter by submission status
`locations`	string[]	—	Filter by location IDs
`users`	string[]	—	Filter by submitter user IDs
`searchText`	string	—	Free-text search
`offset`	number	`0`	Rows to skip
`limit`	number	`1000000`	Page size — set a real value
`includeItems`	boolean	`true`	Include per-item/section answers on each record

Response:

{
  "data": [
    {
      "id": "submission-uuid",
      "name": "Daily Safety Inspection",
      "status": "Approved",
      "progress": 100,
      "createdAt": "2024-12-15T10:30:00Z",
      "updatedAt": "2024-12-15T11:00:00Z",
      "ChecklistId": "template-uuid",
      "DefaultLocationId": "location-uuid",
      "Task": { "id": "task-uuid", "taskNumber": 1234, "title": "Daily Safety Inspection" },
      "Checklist": { "id": "template-uuid", "isScoring": true },
      "SubmissionApproval": { "id": "approval-uuid", "status": "Approved", "totalSteps": 1, "currentStep": 1 }
    }
  ],
  "meta": {
    "totalCount": 150,
    "count": {
      "submitted": 120,
      "Pending Approval": 8,
      "Changes Requested": 2,
      "Approved": 18,
      "Rejected": 2,
      "total": 150
    }
  }
}

Page against meta.totalCount (the total matching-row count). meta.count is an object — a per-status breakdown — not a number. Set includeItems: false for lighter payloads when you only need record-level fields.

Submission Count by Status

Status counts using the same filters as submission records — a cheap way to power a status tile. Endpoint: POST /api/v1/ops/submissions-count-by-status

curl -X POST "https://api.xenia.team/api/v1/ops/submissions-count-by-status" \
  -H "x-client-key: YOUR_CLIENT_KEY" \
  -H "x-client-secret: YOUR_CLIENT_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "checklists": ["template-uuid"],
    "fromDate": "2024-12-01",
    "toDate": "2024-12-31",
    "locations": ["location-uuid"]
  }'

Request Body (all optional): checklists, fromDate, toDate, users, lastItemUpdatedBy, statuses, locations, searchText. Response:

{
  "data": {
    "submitted": { "count": 120 },
    "Pending Approval": { "count": 8 },
    "Approved": { "count": 18 },
    "Rejected": { "count": 2 },
    "total": 148
  },
  "meta": {}
}

Task Analytics

Pre-aggregated task and compliance metrics. All are POST, all respond with { data, meta: {} }, and none of the request bodies are strictly validated (every field is optional).

There are two body shapes. The three “count-by” endpoints take a flat filter object (fromDate, toDate, locations, assignees, taskStatuses, categories, priorities, …). The four location/trend endpoints take a nested filters object with keys location (singular), dateRange ([from, to]), dueDate, schedules, projects, and roles.

Task Count by Status

Endpoint: POST /api/v1/ops/reports/tasks/count-by-status

curl -X POST "https://api.xenia.team/api/v1/ops/reports/tasks/count-by-status" \
  -H "x-client-key: YOUR_CLIENT_KEY" \
  -H "x-client-secret: YOUR_CLIENT_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "fromDate": "2024-12-01",
    "toDate": "2024-12-31",
    "locations": ["location-uuid"],
    "assignees": ["user-uuid"],
    "taskStatuses": ["Open", "Completed"]
  }'

Response — an object keyed by task status (the Open bucket also carries a trend):

{
  "data": {
    "Open": { "count": 45, "trend": 3 },
    "In Progress": { "count": 12 },
    "Completed": { "count": 230 },
    "Missed": { "count": 8 }
  },
  "meta": {}
}

Task Count by Assignees

Endpoint: POST /api/v1/ops/reports/tasks/count-by-assignees Same flat filter body, plus optional assigneeType ("user" | "team" | "location").

curl -X POST "https://api.xenia.team/api/v1/ops/reports/tasks/count-by-assignees" \
  -H "x-client-key: YOUR_CLIENT_KEY" \
  -H "x-client-secret: YOUR_CLIENT_SECRET" \
  -H "Content-Type: application/json" \
  -d '{ "fromDate": "2024-12-01", "toDate": "2024-12-31", "assigneeType": "user" }'

Response — array ordered by count desc:

{
  "data": [
    { "id": "user-uuid-1", "assignee": "John Doe", "count": 50, "assigneeType": "user" },
    { "id": "user-uuid-2", "assignee": "Jane Smith", "count": 35, "assigneeType": "user" }
  ],
  "meta": {}
}

Task Count by Categories

Endpoint: POST /api/v1/ops/reports/tasks/count-by-categories Same flat filter body. Response — array ordered by count desc:

{
  "data": [
    { "id": "service-type-uuid", "category": "Safety", "color": "#FF5A5F", "count": 45 },
    { "id": "NoCategory", "category": "No Category", "color": null, "count": 3 }
  ],
  "meta": {}
}

Weekly Completion Trend

Endpoint: POST /api/v1/ops/reports/tasks/weekly-completion

curl -X POST "https://api.xenia.team/api/v1/ops/reports/tasks/weekly-completion" \
  -H "x-client-key: YOUR_CLIENT_KEY" \
  -H "x-client-secret: YOUR_CLIENT_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "filters": { "location": ["location-uuid"], "dateRange": ["2024-10-01", "2024-12-31"] },
    "view": "schedules",
    "page": 0
  }'

Request Body: filters (nested); view ("schedules" default, or "projects"); page (default 0; negative = past 4-week blocks, positive = future). Response:

{
  "data": {
    "items": [
      {
        "id": "schedule-uuid",
        "title": "Weekly Safety Inspection",
        "schedule": true,
        "weeklyCompletion": [
          { "date": "2024-12-16", "startDate": "2024-12-16", "endDate": "2024-12-22", "percentage": 94.7 }
        ]
      }
    ],
    "weeks": ["Dec 16 - Dec 22", "Dec 09 - Dec 15"],
    "endDate": "2024-12-31",
    "page": 0
  },
  "meta": {}
}

Schedule Completion by Location

Endpoint: POST /api/v1/ops/reports/tasks/schedule-completion-by-location

curl -X POST "https://api.xenia.team/api/v1/ops/reports/tasks/schedule-completion-by-location" \
  -H "x-client-key: YOUR_CLIENT_KEY" \
  -H "x-client-secret: YOUR_CLIENT_SECRET" \
  -H "Content-Type: application/json" \
  -d '{ "filters": { "dateRange": ["2024-12-01", "2024-12-31"] } }'

Request Body: filters (nested); optional locationLevelId (roll stats up to a location level). Response:

{
  "data": {
    "charts": [
      {
        "id": "location-uuid",
        "name": "Downtown Store",
        "totalTasks": 100,
        "Open_Count": 2,
        "InProgress_Count": 3,
        "OnHold_Count": 0,
        "Completed_Count": 95,
        "Missed_Count": 0,
        "CompletedOnTime_Percent": 90,
        "CompletedLate_Percent": 5,
        "Incomplete_Percent": 5
      }
    ],
    "summary": { "completedOnTime": 90 }
  },
  "meta": {}
}

On-Time vs Late by Location

Endpoint: POST /api/v1/ops/reports/tasks/on-time-late-submission-by-location

curl -X POST "https://api.xenia.team/api/v1/ops/reports/tasks/on-time-late-submission-by-location" \
  -H "x-client-key: YOUR_CLIENT_KEY" \
  -H "x-client-secret: YOUR_CLIENT_SECRET" \
  -H "Content-Type: application/json" \
  -d '{ "filters": { "dateRange": ["2024-12-01", "2024-12-31"] } }'

Response (onTime/overdue are percentages):

{
  "data": {
    "charts": [ { "id": "location-uuid", "name": "Downtown Store", "onTime": 94.7, "overdue": 5.3 } ],
    "summary": { "completedOnTime": 94.7 }
  },
  "meta": {}
}

Daily Compliance

Endpoint: POST /api/v1/ops/reports/tasks/daily-compliance Uses its own nested filters keys.

curl -X POST "https://api.xenia.team/api/v1/ops/reports/tasks/daily-compliance" \
  -H "x-client-key: YOUR_CLIENT_KEY" \
  -H "x-client-secret: YOUR_CLIENT_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "filters": {
      "date": "2024-12-23",
      "location": ["location-uuid"],
      "onlyMissed": false
    }
  }'

Request Body: filters.date (single date; defaults to today in the user’s timezone), filters.location (LocationId[]; empty ⇒ the key user’s authorized locations), filters.project (ProjectId[]), filters.onlyMissed (boolean — keep only missed tasks). Response — TaskState is one of Completed, Missed, OverDue, Open:

{
  "data": {
    "charts": [
      {
        "LocationId": "location-uuid",
        "LocationName": "Downtown Store",
        "Projects": [
          { "TaskId": "task-uuid", "ProjectId": "project-uuid", "ProjectTitle": "Evening Safety Check", "TaskState": "Completed" }
        ]
      }
    ]
  },
  "meta": {}
}

Submission Exports

Generate downloadable files from submissions. See the Submission Exports guide for full detail; the essentials:

Export	Endpoint	Behavior
Excel	`POST /api/v1/ops/checklists/{checklistId}/logs-excel`	Async; body `{ recipientEmails, searchString, advanceFilters, advanceItemFilters }`; returns `{ data: { message }, meta: {} }` — delivered by notification/email
PDF	`POST /api/v1/ops/checklists/{checklistId}/logs-pdf`	Async; body `{ logIds, separateFiles }`; returns HTTP 202 `{ status, code, message, data: { requestIds, logIds } }`
Spreadsheet	`POST /api/v1/ops/checklists/submissions-spreadsheet`	Sync; body `{ advanceFilters }`; returns `{ data: { spreadsheetFileDownloadLink }, meta: {} }`
Public PDF	`POST /api/v1/ops/public/submissions/{submissionId}/pdf`	Public (uses an `anonymousid` header, not the client key); requires the submission’s public report to be enabled

The logs-pdf and public-PDF endpoints are the two exceptions to the standard envelope: they return a raw { status, code, message, data } body with HTTP 202 (or 200 when a PDF is already rendered).

Grid Reports

Saved, composable report definitions with per-view configuration, thresholds, and spreadsheet export. Grid reports require the Advanced Dashboards feature on the workspace, plus CAN_VIEW_REPORTING (reads) or CAN_MANAGE_DASHBOARDS (writes).

List Grid Reports

Endpoint: GET /api/v1/mgt/grid-reports

curl -X GET "https://api.xenia.team/api/v1/mgt/grid-reports?offset=0&limit=100" \
  -H "x-client-key: YOUR_CLIENT_KEY" \
  -H "x-client-secret: YOUR_CLIENT_SECRET"

Query: offset (default 0), limit (1–100, default 100). Response: { "data": { "gridReports": [ { "id": "...", "name": "...", "description": "..." } ] }, "meta": {} }

A workspace-scoped form GET /api/v1/mgt/workspaces/{workspaceId}/grid-reports also exists and behaves identically (workspace is otherwise taken from your key).

Create Grid Report

Endpoint: POST /api/v1/mgt/grid-reports

curl -X POST "https://api.xenia.team/api/v1/mgt/grid-reports" \
  -H "x-client-key: YOUR_CLIENT_KEY" \
  -H "x-client-secret: YOUR_CLIENT_SECRET" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Monthly Compliance", "description": "Compliance across all locations" }'

Request Body (both optional): name (≤255), description (≤1000). Returns HTTP 200 { "data": { "gridReport": { ... } }, "meta": {} }.

Create a View

Endpoint: POST /api/v1/mgt/grid-reports/{gridReportId}/view A view captures the metric, grouping, date range, and filters for a grid report. Common fields (all optional, with sensible defaults):

Field	Type	Default	Description
`metric`	string	`"template"`	`"template"` or `"project"`
`displayFormat`	string	`"percentage"`	`"count"`, `"percentage"`, or `"fraction"`
`dateRange`	object	`{}`	`{ from, to, selectedDateOption }` (`from` < `to`)
`dateRangeGrouping`	string	`"daily"`	Grouping bucket
`byHierarchy` / `byProjectRows`	boolean	`false`	Layout toggles
`showRoles` / `showLocations`	boolean	`false`	Break out by role / location
`metricIds` / `locationIds` / `projectIds` / `roleIds`	string[]	`[]`	Scope selectors
`statusFilter`	string	`null`	`completed`, `missed`, `overdue`, or `missedOrOverdue`

Returns { "data": { "gridReportView": { ... }, "viewOrder": ["view-uuid", ...] }, "meta": {} }.

Export a View to Spreadsheet

Endpoint: GET /api/v1/mgt/grid-report-views/{gridReportViewId}/spreadsheet

curl -X GET "https://api.xenia.team/api/v1/mgt/grid-report-views/{gridReportViewId}/spreadsheet" \
  -H "x-client-key: YOUR_CLIENT_KEY" \
  -H "x-client-secret: YOUR_CLIENT_SECRET" \
  --output grid-report.xlsx

Returns the raw XLSX file (not a JSON envelope): Content-Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet with a Content-Disposition: attachment filename.

Configure Thresholds

Attach a color-coded threshold to a view. Endpoint: POST /api/v1/mgt/grid-report-views/{gridReportViewId}/thresholds

curl -X POST "https://api.xenia.team/api/v1/mgt/grid-report-views/{gridReportViewId}/thresholds" \
  -H "x-client-key: YOUR_CLIENT_KEY" \
  -H "x-client-secret: YOUR_CLIENT_SECRET" \
  -H "Content-Type: application/json" \
  -d '{ "color": "#FF5A5F", "label": "Below target", "comparator": "lt", "value": 90 }'

Request Body: color (required), label (required), comparator (required — one of eq, gt, gte, lt, lte, btn), value (required number), secondValue (used with btn). Returns { "data": { "gridReportViewThreshold": { ... } }, "meta": {} }.

Scheduled Reports

Automate generation and delivery of grid reports, task exports, and submission exports on a recurring schedule. Reads need CAN_VIEW_REPORTING; writes need CAN_MANAGE_DASHBOARDS. These routes are workspace-scoped — the /workspaces/{workspaceId} segment is required.

List Report Schedules

Endpoint: GET /api/v1/mgt/workspaces/{workspaceId}/report-schedules

curl -X GET "https://api.xenia.team/api/v1/mgt/workspaces/{workspaceId}/report-schedules?page=1&limit=20" \
  -H "x-client-key: YOUR_CLIENT_KEY" \
  -H "x-client-secret: YOUR_CLIENT_SECRET"

Query (optional): page (default 1), limit (1–100, default 20), search, isActive, frequency (DAILY/WEEKLY/MONTHLY), sortBy, sortOrder. Response:

{
  "data": {
    "reportSchedules": [
      {
        "id": "schedule-uuid",
        "name": "Weekly Compliance Report",
        "reportType": "GRID_REPORT",
        "frequency": "WEEKLY",
        "deliveryTime": "08:00:00",
        "timezone": "America/New_York",
        "isActive": true,
        "ReportScheduleRecipients": [ { "recipientType": "USER", "recipientId": "user-uuid" } ]
      }
    ],
    "pagination": { "page": 1, "limit": 20, "total": 3, "totalPages": 1 }
  },
  "meta": {}
}

Create Report Schedule

Endpoint: POST /api/v1/mgt/workspaces/{workspaceId}/report-schedules

curl -X POST "https://api.xenia.team/api/v1/mgt/workspaces/{workspaceId}/report-schedules" \
  -H "x-client-key: YOUR_CLIENT_KEY" \
  -H "x-client-secret: YOUR_CLIENT_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Weekly Compliance Report",
    "reportType": "GRID_REPORT",
    "reportId": "grid-report-uuid",
    "reportMetadata": { "version": 1, "reportId": "grid-report-uuid", "viewId": "view-uuid", "exportFormat": "XLS" },
    "frequency": "WEEKLY",
    "frequencyConfig": { "daysOfWeek": ["MONDAY"] },
    "deliveryTime": "08:00",
    "timezone": "America/New_York",
    "dateRangeFilter": "LAST_7_DAYS",
    "dataVisibility": "FULL",
    "recipients": [
      { "type": "USER", "id": "user-uuid" },
      { "type": "ROLE", "id": "role-uuid" }
    ]
  }'

Request Body:

Field	Type	Required	Description
`name`	string	Yes	Schedule name (≤255)
`reportType`	string	No	`GRID_REPORT` (default), `TASK_EXPORT`, or `SUBMISSION_EXPORT`
`reportId`	uuid	Conditional	Required for `GRID_REPORT` (here or inside `reportMetadata`)
`reportMetadata`	object	Conditional	Optional for `GRID_REPORT`; required for `TASK_EXPORT` / `SUBMISSION_EXPORT`. Holds `version`, `exportFormat` (`XLS`/`CSV`/`PDF`), and type-specific filters
`frequency`	string	Yes	`DAILY`, `WEEKLY`, or `MONTHLY` (uppercase)
`frequencyConfig`	object	Yes	`{ interval, daysOfWeek, dayOfMonth, weekOfMonth }` — WEEKLY uses `daysOfWeek` (numbers 0–6 or day names), MONTHLY uses `dayOfMonth`
`deliveryTime`	string	Yes	`HH:MM` or `HH:MM:SS`
`timezone`	string	Yes	IANA timezone
`dateRangeFilter`	string	Yes	e.g. `TODAY`, `YESTERDAY`, `LAST_7_DAYS`, `LAST_30_DAYS`, `THIS_MONTH`, `LAST_MONTH`, `THIS_QUARTER`, `THIS_YEAR`
`dataVisibility`	string	Yes	`FULL` or `LOCATION_BASED`
`recipients`	array	Yes	≥1 recipient — each `{ type: USER\|TEAM\|ROLE, id: <uuid> }`

recipients are workspace entities ({ type, id }), not email addresses. There is no schedule wrapper and no top-level format field — frequency, frequencyConfig, deliveryTime, timezone, dateRangeFilter, and dataVisibility are all top-level, and export format lives in reportMetadata.exportFormat.

Returns HTTP 201 { "data": { "reportSchedule": { ..., "ReportScheduleRecipients": [...] } }, "meta": {} }.

Pause / Resume

Endpoint: POST /api/v1/mgt/workspaces/{workspaceId}/report-schedules/{scheduleId}/toggle Body { "isActive": true } (required boolean). Returns { "data": { "reportSchedule": { ... } }, "meta": {} } (the response body carries no message field).

Run Now

Endpoint: POST /api/v1/mgt/workspaces/{workspaceId}/report-schedules/{scheduleId}/run-now Optional body { "force": true } (bypasses the duplicate-run check). Returns:

{
  "data": {
    "scheduleId": "schedule-uuid",
    "scheduleName": "Weekly Compliance Report",
    "jobId": "job-uuid",
    "triggeredAt": "2024-12-23T10:00:00Z",
    "message": "The report is being generated and will be sent to all configured recipients."
  },
  "meta": {}
}

(400 if the schedule has no recipients; 404 if the schedule doesn’t exist.)

Execution History

Endpoint: GET /api/v1/mgt/workspaces/{workspaceId}/report-schedules/{scheduleId}/executions Query (optional): page (default 1), limit (1–100, default 20), status (PENDING/RUNNING/COMPLETED/FAILED), sortBy, sortOrder. Response:

{
  "data": {
    "executions": [
      {
        "id": "execution-uuid",
        "status": "COMPLETED",
        "startedAt": "2024-12-23T08:00:00Z",
        "completedAt": "2024-12-23T08:02:15Z",
        "ReportDeliveries": [ { "status": "sent" } ]
      }
    ],
    "pagination": { "page": 1, "limit": 20, "total": 52, "totalPages": 3 }
  },
  "meta": {}
}

Power BI

For a complete, step-by-step Power BI walkthrough — creating credentials, verifying them, the Power Query (M) examples for POST/GET endpoints and keyed-object responses, scheduled refresh in the Power BI Service, and troubleshooting — see the dedicated Connecting Xenia Data to Power BI guide. In short: use Power BI’s Web connector with a static BaseUrl + RelativePath, put x-client-key / x-client-secret in the request Headers, and set the credential type to Anonymous. Keep queries filtered — the server caps requests at ~60 seconds.

Best Practices

Filter and paginate every pull

Submission records default to an enormous limit. Always send fromDate/toDate and an explicit limit, and page against meta.totalCount. Unbounded pulls risk the ~60s timeout.

Prefer analytics endpoints for aggregates

Don’t recompute compliance/completion in your BI tool from raw records when a /reports/tasks/... endpoint already returns the aggregate — it’s far cheaper and faster.

Automate with scheduled reports

For recurring delivery to people, use scheduled reports (recipients are USER/TEAM/ROLE entities). For live dashboards, pull the analytics/records endpoints on your BI tool’s refresh cadence.

Mind the two analytics body shapes

The count-by-* endpoints take a flat filter object; the location/trend endpoints take a nested filters object with location (singular) and dateRange. Mixing them silently drops filters.

Submission Exports — full detail on Excel/PDF/spreadsheet exports
Task Management — read and write tasks and work orders
Client Key Setup — credentials, headers, and the allow-list

Getting Started

Workflows

Integrations

Reporting & Data Extraction

Overview

Authentication & base URL

Submission Records

Submission Count by Status

Task Analytics

Task Count by Status

Task Count by Assignees

Task Count by Categories

Weekly Completion Trend

Schedule Completion by Location

On-Time vs Late by Location

Daily Compliance

Submission Exports

Grid Reports

List Grid Reports

Create Grid Report

Create a View

Export a View to Spreadsheet

Configure Thresholds

Scheduled Reports

List Report Schedules

Create Report Schedule

Pause / Resume

Run Now

Execution History

Power BI

Best Practices

​Overview

​Authentication & base URL

​Submission Records

​Submission Count by Status

​Task Analytics

​Task Count by Status

​Task Count by Assignees

​Task Count by Categories

​Weekly Completion Trend

​Schedule Completion by Location

​On-Time vs Late by Location

​Daily Compliance

​Submission Exports

​Grid Reports

​List Grid Reports

​Create Grid Report

​Create a View

​Export a View to Spreadsheet

​Configure Thresholds

​Scheduled Reports

​List Report Schedules

​Create Report Schedule

​Pause / Resume

​Run Now

​Execution History

​Power BI

​Best Practices

​Related Guides

Overview

Authentication & base URL

Submission Records

Submission Count by Status

Task Analytics

Task Count by Status

Task Count by Assignees

Task Count by Categories

Weekly Completion Trend

Schedule Completion by Location

On-Time vs Late by Location

Daily Compliance

Submission Exports

Grid Reports

List Grid Reports

Create Grid Report

Create a View

Export a View to Spreadsheet

Configure Thresholds

Scheduled Reports

List Report Schedules

Create Report Schedule

Pause / Resume

Run Now

Execution History

Power BI

Best Practices

Related Guides