API overview

https://atollhq.com

/api/orgs/{orgId}/...

​

When to use the API

• The CLI does not expose the operation you need.
• You are building an integration or automation.
• You need to manage goals, KPIs, initiatives, members, teams, billing, webhooks, or project configuration programmatically.
• You want an agent to use direct HTTP calls instead of a CLI.

​

Request conventions

• Authenticate with Authorization: Bearer sk_atoll_....
• Send JSON request bodies with Content-Type: application/json.
• Request bodies accept camelCase for common fields.
• Some snake_case request fields are accepted for backward compatibility.
• Responses generally use snake_case. Dependency responses retain camelCase release fields (releaseColumnId, releaseColumn, and nested projectId) plus the release_column_id compatibility alias.
• Timestamps are ISO 8601 UTC.
• List endpoints support limit and offset.

​

OpenAPI spec

/openapi.json

​

Minimal helper

atoll() {
  : "${ATOLL_API_KEY:?ATOLL_API_KEY not set}"
  : "${ATOLL_ORG_ID:?ATOLL_ORG_ID not set}"
  curl -sS \
    -H "Authorization: Bearer $ATOLL_API_KEY" \
    -H "Content-Type: application/json" \
    "https://atollhq.com$1" "${@:2}"
}

atoll "/api/orgs/$ATOLL_ORG_ID/issues?limit=10"

​

Core resources