API overview

A public REST API is coming Q2 2026. Email hello@atelyaos.com for early access.

The 30-second version

A general-purpose, API-key-authenticated public REST API for AtelyaOS is on the roadmap for Q2 2026. Until then, the supported automation surfaces are tool integrations (Notion, Google, Slack via OAuth) and outgoing webhooks. If you have a specific integration use case that needs API access today, get in touch.

What's coming

The Q2 2026 public API will cover:

• Workrooms: list, create from a brief payload, fetch state, request revisions.
• Deliverables: trigger export and fetch the resulting file URL.
• Agents: list, get details (custom agent CRUD will come later).
• Credits and billing: read balance, list transactions.
• Webhooks: subscribe to workroom lifecycle events.

Authentication will be via long-lived API keys scoped to a workspace, with role permissions matching the user model.

The plan is for the API to be additive over the existing internal endpoints, not a separate surface — internal endpoints today aren't an API contract you should code against.

What you can do today

Until the public API ships, three patterns cover most automation needs.

1. Tool integrations (OAuth)

Connect Notion, Google Workspace, or Slack from Settings → Integrations → Tools and grant tool access to specific custom agents. This is the right path for "pull a brief from Notion" or "post an approval to Slack".

See tool integrations.

2. Outgoing webhooks

You can configure outgoing webhooks from Settings → Integrations → Webhooks. Outgoing webhooks fire on workroom events and supported integration formats (Slack, Salesforce, Zendesk, Intercom, generic JSON, custom). Each webhook is signed with HMAC for verification.

See webhooks.

3. Custom MCP / webhook bridges

For more bespoke integrations:

• MCP custom server — wire up a Model Context Protocol server you host. Agents can call it as a tool.
• Custom webhook bridge — receive workroom events at any endpoint with HMAC verification.

Available at Settings → Integrations → Tools → MCP / Custom.

Plan gating

API-key authentication and the upcoming public REST API are gated to Growth and above (can_use_api_access flag). Webhook bridges and tool integrations are available across paid tiers; see pricing plans.

Getting early access

If you have a specific use case that the OAuth integrations and webhooks don't cover, email hello@atelyaos.com with:

• The integration you're trying to build.
• The specific endpoints / data you'd need.
• Your timeline.

We're prioritising public API endpoints based on the use cases customers actually want to build. Loud signals here directly affect the order of release.

What's next

• Authentication — API-key model (placeholder).
• Webhooks — what's available today and what's coming.
• Tool integrations — the supported automation path today.