Skip to main content
The Scrums.com API is not yet publicly available. Access is currently limited to design partners and internal teams. This reference documents the API as designed. If you are interested in early access, contact support@scrums.com.

What you can build

The Scrums.com API lets you embed the full Software Engineering Orchestration Platform into your own tooling:
  • Finance and billing dashboards — query Service Line usage, cost accruals, and invoice line items in real time
  • Delivery portals — surface task progress, team health, and ODS deliverables inside your own product
  • Internal automation — trigger agent runs, create tasks, manage talent requests, and react to platform events via webhooks
  • Observability integrations — pull engineering metrics, health scores, and risk signals into your existing reporting stack
  • Access management — provision workspaces, users, and API keys programmatically as part of onboarding workflows

Base URL

https://api.scrums.com/v1

Authentication

All requests require a Bearer token. Tokens are scoped to an organization and optionally narrowed to a workspace.
Authorization: Bearer <token>
API keys are also supported for server-to-server integrations via the same header. See API Keys.

A quick example

Retrieve all active Service Lines for a workspace and get the usage summary for each:
# List active Service Lines
curl https://api.scrums.com/v1/service-lines \
  -H "Authorization: Bearer <token>" \
  -G -d workspace_id=WS-26-000021 \
  -d status=active
{
  "data": [
    {
      "id": "LIN-26-084729",
      "name": "Backend Engineering - Q2 2026",
      "product_line": "talent",
      "execution_model": "capacity",
      "billing_model": "time_and_materials",
      "status": "active"
    }
  ],
  "meta": { "cursor": "eyJpZCI6...", "has_more": false }
}
# Get usage for a specific line
curl https://api.scrums.com/v1/service-lines/LIN-26-084729/usage \
  -H "Authorization: Bearer <token>" \
  -G -d from=2026-04-01 -d to=2026-04-30
{
  "data": {
    "service_line_id": "LIN-26-084729",
    "metrics": [
      { "metric": "talent.hours", "quantity": 640.0, "cost": 60800.00, "currency": "USD" }
    ],
    "total_cost": 60800.00
  }
}

Platform model

Three things make the entire API predictable: 1. The hierarchy is Organization → Workspace → Service Line. Organizations own Workspaces. Workspaces activate Service Lines. Service Lines (LIN-*) are the execution contracts that all delivery, billing, and observability are anchored to. 2. Projects are labels, not hierarchy. A PROJ-* identifier is a tag applied to Service Lines and work items. It groups work across product lines and workspaces without creating structural nesting. There is no “project container” in the hierarchy. 3. Every capability operates through a Service Line. A talent engagement, a managed delivery pod, an ODS outcome scope, infrastructure under management, an intelligence analysis, and a running agent are all LIN-* Service Lines. The Service Line is the universal execution primitive.

Versioning

The current version is v1, declared in the URL path. Breaking changes will be introduced in new versions with advance notice and a deprecation window.

Pagination

All list endpoints use cursor-based pagination:
GET /v1/service-lines?limit=25&cursor=eyJpZCI6IkxJTi0yNi0wODQ3MjkifQ
Responses include meta.cursor for the next page and meta.has_more as a boolean.

Response format

{
  "data": { ... },
  "meta": {
    "cursor": "eyJpZCI6IkxJTi0yNi0wODQ3MjkifQ",
    "has_more": true
  }
}

Errors

{
  "error": {
    "code": "not_found",
    "message": "Service Line LIN-26-084729 not found.",
    "status": 404
  }
}
StatusCodeMeaning
400bad_requestInvalid request parameters
401unauthorizedMissing or invalid token
403forbiddenInsufficient permissions or plan limit exceeded
404not_foundResource does not exist
409conflictState conflict
422unprocessableValidation error
429rate_limitedToo many requests
500server_errorInternal error

Core Platform

Organizations

Top-level entities. All workspaces and billing are scoped here.

Workspaces

Operational units that activate and own Service Lines.

Projects

Labels applied to Service Lines and work items. Not hierarchy.

Users & Roles

Identity, role-based access, and workspace membership.

Plans

Platform tiers that gate which Service Lines can be activated.

Subscriptions

Active plan subscriptions held by an organization.

Service Lines

The central execution primitive. Every capability operates through a LIN-*.

Usage & Metering

Metered usage events and consumption summaries per Service Line.

Billing & Invoices

Invoices and billing history derived from Service Line usage.

Execution API

Cross-platform execution state across all active Service Lines.

Capacity & Allocation

Capacity pools and resource allocation per Service Line.

Observability & Metrics

Platform-wide metrics, health scores, and risk signals.

Incidents & Alerts

Incident tracking and alert configuration per Service Line.

Integrations

Third-party tool connections per workspace.

Webhooks

Event delivery endpoints and configuration.

API Keys

API key management for server-to-server access.

Audit Logs

Immutable audit trail for all platform actions.

Events

Platform event stream and structured event records.

Tasks & Work Items

Work items linked to Service Lines and project labels.

Product Lines

Talent Marketplace

Talent supply, matching, allocation, and staffing. Mints LIN-* on engagement.

Managed Services

SLA-based delivery pods under Scrums coordination. Mints LIN-* on activation.

ODS

Scoped, time-boxed outcome delivery. Buy a result, not a sprint.

Platforms & Infrastructure

Infrastructure and platform engineering management. Mints LIN-* per estate.

Developer Intelligence

Engineering metrics, delivery insights, scorecards, and risk.

AI Agent Gateway

Governed agent execution with policies, audit, and tool access control.
Last modified on April 15, 2026