TeamGrid developer documentation

First request

Authenticate with a reveal-once credential and call the regional endpoint that credential encodes.

curl --fail-with-body \
  --header "Authorization: Bearer $TEAMGRID_API_TOKEN" \
  --header 'Accept: application/json' \
  https://api.de.teamgrid.app/v1/workspace

The response identifies the authenticated workspace, its region, and its cell. The quickstart covers creating the credential, listing tasks, and paginating with cursors.

Interfaces

API v1 is the source of truth. The other three interfaces are clients of it rather than independent integration surfaces.

API v1The versioned HTTP contract: scoped credentials, regional ingress, cursor pagination, idempotent creates, and signed webhooks.TypeScript SDKA typed Node.js client with regional routing, bounded retries, timeouts, pagination iterators, and versioned errors.CLIInspect and automate TeamGrid from a terminal or a CI job, with structured output and stable exit codes.MCP serverAn optional local stdio adapter with a deliberately bounded read-only tool surface, using the same credentials as the CLI.

API v1 1.0.0-beta.2 governs 181 operations across 111 paths. That number measures contract parity across the HTTP API, SDK, and CLI, not complete TeamGrid product coverage. The capability ledger records the remaining partial, planned, and private areas explicitly, and choose an interface maps common integration shapes to a recommended surface.

Existing v0 integrations

API v0 remains available for compatibility. Its contract is frozen and documented separately, with migration guidance beside the legacy reference.

API v0 documentationMigrate to v1OpenAPI filesChangelogSecurity