> ## Documentation Index
> Fetch the complete documentation index at: https://www.composer.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> composerID is an API that publishes a workforce decision reference into the systems that execute it. Start here.

**One reference for every workforce decision, in every system that acts on it.**

composerID is a REST API. [Triage](https://www.addtriage.com) decides how a request for work is filled: a contractor, a permanent hire, a statement of work or an outsourced team. composerID mints one reference for that decision, the Intent ID, and publishes it into the systems that execute it: vendor management, HRIS, ATS, ERP, contract management and source-to-pay. Each destination keeps its own records and its own numbers. Every one of them carries the same Intent ID back to the decision that caused the work.

The API is five calls long. You create an intent, plan where it goes, preflight it against the destination's rules, publish, and read back a timeline of everything that happened. Publishing is idempotent: a retry returns the original receipt instead of creating a second record.

<Note>
  The hosted sandbox at `https://sandbox.composer.id/v1` serves the whole documented API against mock destination tenants. Mint your own credentials at `POST /sandbox/keys`; no sign-up. The production service at `api.composer.id` is in build.
</Note>

## Documentation

<Columns cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Mint a sandbox key and publish your first decision in five calls.
  </Card>

  <Card title="Concepts" icon="lightbulb" href="/concepts/how-it-works">
    The Intent Record, publishing, events and the Compliance File.
  </Card>

  <Card title="API reference" icon="code" href="/api-reference/overview">
    Every `/v1` route, generated from the OpenAPI document, with a live playground.
  </Card>

  <Card title="Destinations" icon="plug" href="/destinations">
    Fifty-two destination systems and the field the Intent ID lands in.
  </Card>

  <Card title="Webhooks and events" icon="webhook" href="/concepts/events">
    Signed destination events, verified and correlated to the Intent ID.
  </Card>

  <Card title="Guides" icon="map" href="/guides/lifecycle">
    Publish end to end, connect a destination, and the Beeline walkthrough.
  </Card>
</Columns>

## Where to start

* New here: start at the [Quickstart](/quickstart). It ends with a published decision and a receipt.
* Connecting a system: read [Connect a destination](/guides/connect), then the page for your destination.
* Looking up a route, a field or a scope: the [API reference](/api-reference/overview) and [Authentication](/authentication).