Fields and enums

Request bodies accept camelCase for common fields. Resource responses generally use snake_case; auth context uses the camelCase field names shown below.

Auth context

GET /api/auth/me returns one of two auth shapes. Human sessions include type: "human", userId, and orgId. Agent keys additionally include agentId, memberType, scopes, the live organization role, and projectAccess. OAuth-bound agent responses also include the non-secret oauth provenance object:

{
  "auth": {
    "type": "agent",
    "userId": "member-uuid",
    "orgId": "org-uuid",
    "agentId": "member-uuid",
    "memberType": "agent",
    "scopes": [],
    "role": "guest",
    "projectAccess": [
      {
        "projectId": "project-uuid",
        "accessLevel": "admin"
      }
    ],
    "oauth": {
      "authorizedByMemberId": "human-member-uuid",
      "clientId": "oauth-client-id",
      "resource": "https://atollhq.com/mcp",
      "clientName": "ChatGPT",
      "connectionId": "connection-uuid",
      "profileRef": "profile-grant-uuid"
    }
  }
}

auth.oauth is present only for OAuth 2.1 access tokens. It identifies the consenting human, OAuth client, and exact protected resource; it never contains an access token, refresh token, or API key. API-key agent responses omit this object.

OAuth agent profiles

GET /api/oauth/agent-profiles returns the exact MCP resource and only the connection’s currently usable grants:

{
  "resource": "https://atollhq.com/mcp",
  "profiles": [{
    "profile_ref": "profile-grant-uuid",
    "display_name": "Product Planner",
    "designation": "Project-scoped agent",
    "organization": { "id": "org-uuid", "name": "Atoll" },
    "projects": [{
      "id": "project-uuid",
      "name": "Atoll HQ",
      "access_level": "edit"
    }]
  }]
}

The profile reference is server-minted, opaque, and connection-scoped. It is not a credential and must not replace the bearer token or become shared mutable active-profile state. Project-scoped agents remain organization guests. projectAccess is the effective per-project authorization and is resolved from current membership data on every request. Key rotation is not required after role or project membership changes.

Avatar upload response

Successful POST /api/orgs/{id}/members/{memberId}/avatar requests return 200 with only the target member identifier and avatar URL:

{
  "member": {
    "id": "member-uuid",
    "avatar_url": "https://..."
  }
}

No other member, invitation, onboarding, or account metadata is included. If the member pointer is updated but removal of the retired Storage object is still pending, the endpoint returns 202 with the same member projection plus "cleanup_pending": true. The DELETE endpoint likewise returns { "success": true, "cleanup_pending": true } with 202 when durable cleanup is queued. A concurrent pointer change returns { "error": "Avatar changed concurrently" } with 409; it includes the optional "cleanup_pending": true only if cleanup of a staged or retired object remains queued. A service-only scheduled worker drains due cleanup jobs every 15 minutes, with avatar requests providing an additional opportunistic sweep. Uploads over 2MB return 413.

Task fields

{
  "title": "Fix login bug",
  "description": "Markdown supported",
  "status": "todo",
  "priority": 1,
  "assigneeId": "member-uuid",
  "assigneeIds": ["member-uuid-1", "member-uuid-2"],
  "projectId": "project-uuid",
  "milestoneId": "milestone-uuid",
  "teamId": "team-uuid",
  "startDate": "2026-03-01",
  "dueDate": "2026-04-01",
  "recurrenceType": "weekly",
  "recurrenceInterval": 1,
  "recurrenceDays": ["mon", "wed", "fri"],
  "labelIds": ["label-uuid-1", "label-uuid-2"]
}

Most fields work on create and update unless a route says otherwise. labelIds is accepted on task create and bulk create. For existing tasks, use the label endpoints or atoll label add/remove. startDate and dueDate are date-only values in YYYY-MM-DD format. Recurring tasks use dueDate to compute the next generated task when the current task moves to done. Weekly tasks may set recurrenceDays to a unique array of weekday values from mon through sun. Responses normalize this as recurrence_days and expose { type, interval, days } in recurrence_schedule. Task detail responses include enriched member objects for creator, assignee, and assignees; each creator/assignee object includes id, display_name, type, and avatar_url when available. Full GET /api/orgs/{id}/issues list items include identifier, the canonical project-prefixed issue reference, and projectSlug, the collision-free project route segment. Both are null for projectless issues. Compact view=board and view=list items do not include these fields.

Task Activity fields

GET /api/orgs/{id}/activity returns { data, currentMemberId, limit, offset, hasMore }; it accepts limit, offset, and filter=all|by_me|mine. GET /api/orgs/{id}/issues/{issueId}/activity returns { data, items, limit, offset, hasMore }. Each event retains the activity_events fields. Top-level actor is a current member projection and can reflect later profile changes; the immutable event-time actor snapshot is metadata.actor with id, display_name, type, and avatar_url. The canonical action values are: issue.created, issue.updated, issue.archived, issue.unarchived, comment.created, comment.updated, comment.deleted, assignee.added, assignee.removed, label.added, label.removed, dependency.added, dependency.removed, dependency.release_updated, initiative.linked, initiative.unlinked, initiative_target.linked, initiative_target.unlinked, github_pr.linked, github_pr.updated, attachment.added, attachment.removed, subtask.created, subtask.completed, subtask.reopened, subtask.removed, and subtask.updated. metadata contains safe event snapshots and before/after changes. Notification, webhook, realtime, and delivery records are excluded. Pre-contract history may be partial because older events are not fabricated or backfilled.

Dependency fields

Dependency creation requires the blocking issue to belong to a project because the persistent release point is a board column in that project. A projectless issue may be the blocked target when the caller has permission to use it. GET /api/orgs/{id}/issues/{issueId}/dependencies returns blocking and blockedBy arrays. Each entry includes:

Response field	Type	Notes
`id`	UUID	Dependency identifier
`issue`	object or null	Authorized target projection with `id`, `number`, `identifier`, `projectSlug`, `title`, and `status`; inaccessible targets are `null`
`issue.identifier`	string or null	Canonical project-prefixed issue reference; `null` for projectless targets
`issue.projectSlug`	string or null	Collision-free project route segment; `null` for projectless targets
`createdAt`	timestamp	Dependency creation time
`releaseColumnId`	UUID	Persistent release column in the blocking issue’s project
`release_column_id`	UUID	Snake-case compatibility alias for `releaseColumnId`
`releaseColumn`	object or null	`{ id, key, label, position, projectId }` release column projection
`satisfied`	boolean or null	Whether the blocker reached the release column position, or is cancelled

Release-column fields are returned when the blocking issue is authorized. In the blocking list, the dependent target projection may be issue: null independently when that target is inaccessible. The dependency-release migration backfills existing dependencies to the blocking project’s done column before enforcing the persistent reference. During a rolling deployment, compatibility reads may omit release fields from older rows; treat missing release metadata as the legacy open-blocker behavior until the migration is applied.

Goal fields

{
  "title": "Reach 100 paying customers by Q2",
  "description": "Primary growth objective",
  "owner_id": "member-uuid",
  "status": "active",
  "target_date": "2026-06-30"
}

KPI fields

{
  "name": "paying_customers",
  "description": "Total active paying customers",
  "goal_id": "goal-uuid",
  "unit": "count",
  "unit_label": "customers",
  "target_value": 100,
  "target_direction": "increase",
  "source_type": "manual",
  "stale_after_hours": 168
}

Calculated task-completion KPIs use source_type: "formula" and are calculated from linked work instead of snapshots:

{
  "name": "mvp_tasks_done",
  "goal_id": "goal-uuid",
  "source_type": "formula",
  "source_config": {
    "formula": "goal_linked_issue_completion",
    "done_statuses": ["done"]
  }
}

For goal_linked_issue_completion, current_value is the count of non-archived directly linked issues and milestone-linked issues in done status and target_value is the total non-archived directly linked issue and milestone-linked issue count under initiatives for the goal.

KPI snapshot fields

{
  "value": 34,
  "source": "agent",
  "attribution_note": "Checked Stripe dashboard",
  "attributed_to_initiative_id": "initiative-uuid",
  "attributed_to_issue_id": "issue-uuid"
}

Recording a snapshot updates the KPI’s current_value. KPI-to-initiative impact links are separate from snapshot attribution. A link means the initiative is expected to move the KPI; snapshot attribution identifies the initiative and/or issue that produced one measurement. Calculated KPIs do not accept manual snapshots. api_poll snapshots are written by published KPI HTTP Syncs and include first-class provenance: source_sync_id, source_sync_run_id, source_config_hash, source_recorded_for, observed_at, and optional provider_recorded_at.

KPI detail relationship fields

GET /api/orgs/{id}/kpis/{kpiId} adds initiative_impacts to the kpi object. Each row represents an intended-impact relationship and includes the relationship identifiers, expected_impact, and a visible initiative object with its id, title, name, and status. The rows cover all initiative statuses and are filtered through project-aware initiative visibility. This is not KPI snapshot attribution.

{
  "kpi": {
    "id": "kpi-uuid",
    "name": "paying_customers",
    "initiative_impacts": [{
      "id": "impact-uuid",
      "initiative_id": "initiative-uuid",
      "kpi_id": "kpi-uuid",
      "expected_impact": "+30 customers/mo",
      "initiative": {
        "id": "initiative-uuid",
        "title": "Content pipeline",
        "name": "Content pipeline",
        "status": "completed"
      }
    }]
  }
}

KPI HTTP sync fields

{
  "name": "PostHog visitors",
  "status": "draft",
  "schedule": "daily",
  "request_config": {
    "method": "GET",
    "url": "https://us.posthog.com/api/projects/123/query/",
    "headers": {
      "Authorization": {
        "secretRef": "posthog_api_key",
        "format": "Bearer {value}"
      }
    }
  },
  "extraction_config": {
    "contentType": "json",
    "pointer": "/results/0/value",
    "numeric": {
      "mode": "number",
      "percentageScale": null
    }
  },
  "freshness_config": {},
  "config_version": 1,
  "config_hash": "sha256:..."
}

KPI HTTP Syncs are constrained generic pollers: GET only, https only, JSON only, exact-host allowlisted, no redirects, no request bodies, no query strings, and no secret values in configs. Draft creation and config validation require the destination host to already be exactly allowlisted. Credential placeholders are limited to Authorization: Bearer <secretRef> and X-API-Key: <secretRef>. Human admins manage exact-host allowlists, secrets, dry-runs, publish, disable, and snapshot-writing run-now actions in Settings > Integrations > KPI syncs. Machine actors can create draft syncs and validate proposed configs only after the host is allowlisted. The org-wide Settings endpoint returns config and secret metadata only to human owners/admins; non-admin members receive redacted status rows, and guests/machine actors are denied.

KPI HTTP sync run fields

{
  "status": "success",
  "recorded_for": "2026-06-03T00:00:00.000Z",
  "observed_at": "2026-06-03T00:01:04.000Z",
  "provider_recorded_at": null,
  "http_status": 200,
  "duration_ms": 348,
  "response_bytes": 2048,
  "extracted_value": 1234,
  "snapshot_id": "snapshot-uuid",
  "error_code": null,
  "redacted_error": null
}

Run history is sanitized. It does not expose request headers, secret values, response bodies, or raw third-party payloads.

Board column mutation fields

Create a column with key, label, optional description, and optional color; it appends to the board. Patch accepts label, description, and color. Create and patch reject position—use the reorder endpoint instead. Delete a column with DELETE .../board-columns/{columnId}?reassignTo={targetColumnId}&releaseReassignTo={releaseTargetColumnId}. reassignTo is required when the source column contains issues and must name a column in the same project. releaseReassignTo is a separate target and is required when the source has dependency release references. The board-column list reports issue_count and release_reference_count so clients can fail closed before deletion. Reassignment and deletion are atomic, and the final board column cannot be deleted. Reorder with { "columns": [{ "id": "column-uuid", "position": 0 }] } and include every current column exactly once with unique non-negative positions.

Initiative fields

{
  "title": "Launch self-serve onboarding flow",
  "description": "Reduce friction for new signups",
  "goal_id": "goal-uuid",
  "owner_id": "member-uuid",
  "status": "active",
  "target_date": "2026-05-15",
  "project_id": "project-uuid"
}

Create requests accept either title or legacy name; Atoll stores both fields from the trimmed value. Create requests also accept goalId, ownerId, targetDate, and projectId aliases for goal_id, owner_id, target_date, and project_id. Guest/project-scoped callers must use project_id and have edit/admin access to that project. GET /api/orgs/{id}/initiatives/{initiativeId} adds kpi_impacts to the initiative object. Only relationships whose linked KPIs are readable by the caller are embedded; unreadable KPI relationships are omitted. The rows are intended-impact links, not snapshot attribution records.

{
  "initiative": {
    "id": "initiative-uuid",
    "title": "Content pipeline",
    "kpi_impacts": [{
      "id": "impact-uuid",
      "org_id": "org-uuid",
      "initiative_id": "initiative-uuid",
      "kpi_id": "kpi-uuid",
      "expected_impact": "+30 customers/mo",
      "created_at": "2026-08-17T00:00:00Z"
    }]
  }
}

Initiative link fields

Initiative issue links and initiative-target issue links accept the following request shape:

{ "issue_id": "ATOLL-42" }

issue_id may be an issue UUID, a bare number, #number, ATOLL-number, TSK-number, or an unambiguous project-derived prefix. Initiative milestone links use:

{ "milestone_id": "Public beta" }

milestone_id may be a milestone UUID or its exact name. Resolution is scoped to the initiative’s authoritative projects and successful writes persist the canonical resource UUID. Target milestone links remain UUID-addressed.

Automation rule fields

{
  "name": "Auto-assign urgent bugs",
  "trigger_event": "issue.created",
  "conditions": [
    { "field": "priority", "operator": "eq", "value": 0 }
  ],
  "actions": [
    { "type": "set_assignee", "value": "member-uuid" }
  ],
  "enabled": true,
  "project_id": "project-uuid"
}

Dry-run test body:

{
  "issue_id": "issue-uuid"
}

or:

{
  "issue": {
    "status": "todo",
    "priority": 2
  }
}

Custom view fields

{
  "name": "My sprint view",
  "filters": { "status": ["in_progress", "todo"], "priority": [0, 1] },
  "sort": { "field": "priority", "direction": "asc" },
  "display_mode": "board",
  "color": "#6B7280",
  "icon": "list"
}

Webhook fields

{
  "url": "https://example.com/webhook",
  "events": ["issue.created", "issue.updated"],
  "enabled": true
}

The URL must be an HTTPS DNS hostname. IP literals, localhost, and .local hosts are rejected at creation; delivery refuses non-public DNS results and does not follow redirects. The create response includes a secret for HMAC verification. Store it immediately; it is shown only once. List responses include destination_display and a deprecated url compatibility field; both contain only the origin plus /…. Delivery requests include X-Atoll-Signature, X-Atoll-Signature-Version, versioned X-Atoll-Signatures, and X-Atoll-Delivery-Id. Payload schema version 2 is allowlisted and omits descriptions, comment bodies, and raw change values. Delivery history includes delivery_id, status, status_code, error_code, delivered_at, and next_retry_at; it never includes payloads, receiver response bodies, or raw errors.

Private inbox fields

Field	Meaning
`status`	`untriaged`, `triaged`, `action_required`, `waiting`, `resolved`, `ignored`, or `quarantined`
`category`	`support`, `security`, `sales`, `partnership`, `press`, `personal`, `spam`, `other`, or `null`
`priority`	Integer from `0` (urgent) through `4` (low)
`mailbox`	Allowed recipient alias that accepted the message
`sender`	Provider-normalized sender object
`body_text`	Plain-text message body
`body_html_sanitized`	HTML with active content and remote images removed
`ingestion_status`	`pending`, `complete`, `failed`, or `quarantined`
`retain_until`	One-year retention deadline assigned at ingestion
`linked_issue_id`	Optional issue UUID in the same organization
`attachments[]`	Private attachment metadata; bytes require the authenticated attachment content route
`actions[]`	Append-only ingestion and operator audit records
`drafts[]`	Saved plain-text reply drafts; drafts are not sent

List responses omit message bodies, headers, action history, and drafts. Use the single-message endpoint only after selecting a queue item.

Strategy audit fields

GET /api/orgs/{id}/strategy/audit returns findings (sorted critical → warning → info), a summary, and counts_by_type. Each finding:

Field	Type	Description
`type`	string	Finding type (see values below)
`severity`	string	`critical`, `warning`, or `info`
`title`	string	Short human-readable summary
`message`	string	Why it matters
`suggested_fix`	string	Concrete next action (usually the exact API call)
`goal_id` / `kpi_id` / `initiative_id` / `initiative_target_id` / `issue_id` / `milestone_id` / `project_id`	string	Whichever entity ids apply

Finding type values: initiative_orphaned, kpi_orphaned, goal_missing_kpi, goal_missing_initiative, dangling_initiative_project, dangling_initiative_issue, dangling_initiative_milestone (structural); kpi_unrecorded, kpi_missing_target, kpi_stale, kpi_off_pace (KPI health); initiative_missing_impact, initiative_missing_execution, initiative_stalled, initiative_target_missing_execution, initiative_target_overdue, initiative_target_blocked (initiative health); issue_blocked, issue_overdue, milestone_overdue (execution). Strategy audit findings are active-context findings. Paused and cancelled goals are excluded from active goal checks, KPIs attached to inactive goals are skipped for KPI health checks, and paused, completed, or cancelled initiatives are skipped for initiative health checks.

Enums

Domain	Field	Values
Task	`status`	Project-defined stored board-column key matching `^[a-z0-9_]+$`; defaults are `backlog`, `todo`, `in_progress`, `done`, with system status `cancelled`
Board column	`description`	Optional Markdown/plain-text stage criteria or agent guidance; `null` means no guidance
Task	`priority`	`0`, `1`, `2`, `3`
Task update request	`comment_body`	Optional Markdown/plain text or rich-text HTML comment body created with the issue update; stored and returned as sanitized HTML
Task update request	`comment_mentions[].member_id`	Stable Atoll org member ID to mention in the issue update comment created by `comment_body`; not an auth user ID or display name
Comment create request	`mentions[].member_id`	Stable Atoll org member ID to mention in a direct comment API request; recommended for agents and integrations
Comment create response	`outcome.persistence`	`{ status: "persisted", comment_id }`; comment durability is independent of notification and transport state
Comment create response	`outcome.mentions.created`	Count of new notification rows created for resolved mention recipients
Comment create response	`outcome.mentions.deduped`	Count of existing idempotent notification rows reused for duplicate or retried mentions
Comment create response	`outcome.mentions.notification_rows`	Creation, deduplication, skip, and failure counts; setup failure does not make the persisted comment a failure
Comment create response	`outcome.mentions.transport`	Asynchronous Google Chat dispatch state; `scheduled` is not final delivery, `final` is null while any result is unknown, `mixed` means terminal recipient results differ, and `error` exposes safe lookup/scheduling failure details
Comment create response	`outcome.mentions.skipped[]`	Mention targets that did not create notification rows; each includes `member_id` and `reason`
Comment list response	`comments[].mentioned_members[]`	Persisted mention recipient summary with `id`, nullable `display_name`, and nullable `type`; empty when no mentions are recorded
Task	`recurrenceType`	`daily`, `weekly`, `biweekly`, `monthly`, `custom`
Weekly task	`recurrenceDays[]`	Unique `mon`, `tue`, `wed`, `thu`, `fri`, `sat`, `sun` values
Goal	`status`	`active`, `achieved`, `missed`, `paused`, `cancelled`
KPI	`unit`	`count`, `percentage`, `currency`, `duration`, `ratio`, `custom`
KPI	`target_direction`	`increase`, `decrease`, `maintain`
KPI	`source_type`	`manual`, `webhook`, `api_poll`, `formula`
KPI snapshot	`source`	`manual`, `webhook`, `api_poll`, `formula`, `agent`
KPI HTTP sync	`status`	`draft`, `published`, `disabled`
KPI HTTP sync run	`status`	`queued`, `running`, `success`, `error`
Initiative	`status`	`proposed`, `active`, `completed`, `paused`, `cancelled`
Initiative target	`mode`	`progress`, `gate`
Initiative target	`target_direction`	`increase`, `decrease`, `maintain`
Status update	`status`	`on_track`, `at_risk`, `off_track`
Member	`role`	`owner`, `admin`, `member`, `guest`
Project member	`accessLevel`	`view`, `edit`, `admin`
Automation	`trigger_event`	`issue.created`, `issue.status_changed`, `issue.assigned`, `issue.priority_changed`
Heartbeat signal	`severity`	`info`, `warning`, `critical`
Heartbeat attention	`attention_items[]`	Direct current-member notifications such as mentions, assignments, assignee comments, and creator-visible status changes
Heartbeat attention	`attention_items[].ack_endpoint`	Org-scoped endpoint to acknowledge the notification after it is handled
Heartbeat attention	`attention_items[].comment_id`	New comment that caused a comment attention item
Heartbeat attention	`attention_items[].reply_to_comment_id`	Parent comment for a direct reply, when present
Heartbeat attention	`attention_items[].routing`	Validated parent agent provenance (`harness`, thread/session ID, optional host ID) for deterministic resume
Heartbeat attention	`attention_summary.total_unread`	Count of unread actionable attention items included in the heartbeat
Notification	`event_type`	`mention.created`, `issue.assigned`, `comment.added`, `issue.status_changed`
Notification preference	`event_type`	Notification event type: `mention.created`, `issue.assigned`, `comment.added`, or `issue.status_changed`; disabling in-app mentions also attempts to acknowledge currently unread mention notifications
Notification preference	`channel`	Delivery channel: `in_app` or `google_chat`; the single Google Chat preference is stored under `mention.created` and controls mentions, assignments, and direct-reply comments; ordinary comments and status changes are excluded, and the channel is independent from in-app notifications
Google Chat callback	`message.text`, `message.argumentText`	Message or parsed command text accepted for `help` and `connect`; plain `help`, `/help`, and `@Atoll help` are equivalent
Google Chat classic callback	`message.slashCommand.commandId`	Configured Help command ID `1`
Google Chat add-on callback	`chat.appCommandPayload.appCommandMetadata.appCommandId`	Configured Help command ID `1`; metadata can also include `appCommandType`
Google Chat status	`chatAppUrl`	URL used by Atoll’s setup UI to open Google Chat or a dedicated Atoll Chat app/listing page when configured
Google Chat config session	`session`	Short-lived Chat identity preview with `googleUserDisplayName`, `googleUserEmail`, and `expiresAt`; the raw token stays in an HttpOnly cookie and the Google completion redirect is never returned by `GET`
Google Chat config session	`memberships[]`	Atoll workspace memberships owned by the authenticated human and eligible for selection
Google Chat member status	`linked`	Whether the current member has an active Google Chat direct-message link
Google Chat member status	`googleUserDisplayName`, `googleUserEmail`	Display-safe identity details for the current member’s active link
Google Chat member response	`chatAppUrl`	Configured Atoll Chat app URL used by the Connected Apps setup UI; falls back to Google Chat home
Google Chat link token	`command`	Manual fallback setup message generated from Connected Apps settings by an authenticated human web session and consumed by the Google Chat event callback; API keys cannot create it
Notification preference	`enabled`	Whether the current member wants this event/channel delivered
Heartbeat project context	`board_columns[].description`	Optional board-column guidance surfaced to agents in `heartbeat --json`
Heartbeat initiative context	`project_ids`	Project IDs connected to an initiative through project, milestone, or issue links
Heartbeat initiative context	`linked_issues`	Accessible issue evidence used for initiative health and recommendations
Heartbeat initiative context	`targets[]`	Initiative target context with linked work, completion, due-soon, overdue, and blocked state
Heartbeat recommendation	`recommended_action.action_type`	`create_work`, `start_work`, `escalate_blocker`, `refresh_metric`, `investigate`; `defer_busywork` is reserved
Heartbeat recommendation	`suggested_write.operation`	`issue.create`, `issue.update`, `comment.add`, `kpi.snapshot.request`, `none`
Heartbeat recommendation	`quality_checks[].status`	`pass`, `warning`
Heartbeat recommendation	`usage_guidance.preserve_fields[]`	Field names agents should preserve in issue, KPI, status update, or comment writes
Heartbeat recommendation	`usage_guidance.avoid_payload_sources[]`	Context categories agents should avoid copying into write payloads
Custom view	`display_mode`	`board`, `list`
Inbox email	`status`	`untriaged`, `triaged`, `action_required`, `waiting`, `resolved`, `ignored`, `quarantined`
Inbox email	`category`	`support`, `security`, `sales`, `partnership`, `press`, `personal`, `spam`, `other`
Inbox email	`priority`	`0` (urgent) through `4` (low)

See Heartbeat API for the full recommended_action shape, suggested write fields, and response examples. Initiative targets use fields title, description, mode, unit, unit_label, current_value, target_value, target_direction, target_date, and due_soon_days. Use mode: "progress" for initiative output tracking and mode: "gate" for hard prerequisites. Gate target heartbeat messages use stateful language like 0/5 retailers complete; they do not emit KPI pace.

Start here

User guide

Agent guide

CLI

API reference

Integrations

Admin

Changelog

Troubleshooting

Auth context

OAuth agent profiles

Avatar upload response

Task fields

Task Activity fields

Dependency fields

Goal fields

KPI fields

KPI snapshot fields

KPI detail relationship fields

KPI HTTP sync fields

KPI HTTP sync run fields

Board column mutation fields

Initiative fields

Initiative link fields

Automation rule fields

Custom view fields

Webhook fields

Private inbox fields

Strategy audit fields

Enums

​Auth context

​OAuth agent profiles

​Avatar upload response

​Task fields

​Task Activity fields

​Dependency fields

​Goal fields

​KPI fields

​KPI snapshot fields

​KPI detail relationship fields

​KPI HTTP sync fields

​KPI HTTP sync run fields

​Board column mutation fields

​Initiative fields

​Initiative link fields

​Automation rule fields

​Custom view fields

​Webhook fields

​Private inbox fields

​Strategy audit fields

​Enums

Auth context

OAuth agent profiles

Avatar upload response

Task fields

Task Activity fields

Dependency fields

Goal fields

KPI fields

KPI snapshot fields

KPI detail relationship fields

KPI HTTP sync fields

KPI HTTP sync run fields

Board column mutation fields

Initiative fields

Initiative link fields

Automation rule fields

Custom view fields

Webhook fields

Private inbox fields

Strategy audit fields

Enums