Connect Alloy through APIs

Use API access when work starts outside the Alloy app. A product event, backend job, customer action, or internal system can send data into Alloy and start the right process.

Common examples include uploading files to organization storage, creating folders, moving or renaming files, downloading stored files, or triggering a workflow from another system.

Alloy's private API is scoped to an organization and uses an organization private API key in the `api-key` header.

The current private API includes storage routes and workflow trigger routes. Storage routes can list folders, upload files, read metadata, download files, create folders, rename, move, and delete files or folders. Trigger routes can start a workflow by workflow ID with a JSON payload.

AI teammates can also be configured with the `API` channel. When an AI teammate uses this channel, the AI teammate's detail page includes an API tab with an endpoint, request examples, a built-in request tester, and request logs filtered from workflow runs.

Use this when a specific AI teammate needs to be callable from another product or backend process.

Private storage uploads currently allow files up to 10 MB. If a file with the same name already exists at the target path, the upload overwrites it.

Workflow triggers return a run ID when the workflow starts successfully. If the workflow is missing or does not have a configured starting step, the API returns an error instead of starting work.