> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get-hive.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Developer overview

> What developers can build on Hive today — signed incoming webhooks, public workflow forms, MCP servers, workflow export and import — and what is not available yet.

Hive is designed to plug into the systems you already run. Most teams never write code: they connect tools with OAuth, build workflows in the builder, and configure agents in Agent Studio. When you do want to build something custom, this page maps the ways in that exist today.

<Note>
  Hive does **not** currently offer a general customer REST API with personal API keys, or outgoing webhooks. The product's own API is authenticated with signed-in user sessions and is not a supported integration surface. If you need programmatic access that the options below do not cover, [tell us what you are building](/help/support).
</Note>

## What you can build with today

<CardGroup cols={2}>
  <Card title="Incoming webhooks" icon="bolt" href="/integrations/incoming-webhooks">
    Push signed JSON events from any system into Hive — ideal for tools without a native connector, or bridges from Zapier or Make.
  </Card>

  <Card title="Public workflow forms" icon="file-lines" href="/developers/public-form-api">
    Start a deployed workflow from your website or another system by submitting its public form.
  </Card>

  <Card title="MCP servers" icon="server" href="/integrations/mcp-servers">
    Connect any Model Context Protocol server over HTTPS and let Hive use its tools, under approval.
  </Card>

  <Card title="Workflow export and import" icon="file-export" href="/developers/workflow-export-format">
    Export a workflow as JSON, keep it in version control, and import it into another workspace.
  </Card>
</CardGroup>

### Incoming webhooks: send data into Hive

Create a webhook in **Integrations → Add integration → Incoming webhook**. Hive gives you a unique URL and a signing secret, shown once. Your system sends JSON with an `X-Hive-Signature` header — a hex HMAC-SHA256 of the raw body — and Hive acknowledges with `202`.

* Typed business events (`proposal.created`, `proposal.won`, `client.created`) feed Hive's certified sources and signals.
* Any other valid JSON is still accepted and ingested as a generic event.
* Duplicate deliveries are recognised and acknowledged without being processed twice.

Signing examples in several languages are in [Webhook signing](/developers/webhook-signing).

### Public workflow forms: start work from outside Hive

A workflow with a **Public form** trigger has a link anyone can submit, without signing in. Behind that link is a small, rate-limited HTTP interface you can call yourself — for example from a contact form on your website — with an idempotency key so retries never start a second run. See [Public form API](/developers/public-form-api).

### MCP servers: bring your own tools

Hive is an MCP **client**. Connect a curated server (Notion, Linear, Sentry, Stripe) in one click, or any Streamable HTTP MCP server by URL with no auth, a bearer token, or OAuth 2.1. Hive discovers the tools, pins a fingerprint of each one, and treats them as high-risk actions that go through approval. See [MCP servers](/integrations/mcp-servers).

<Info>
  Hive does not expose its own MCP server today.
</Info>

### Workflow export and import: workflows as code

Every workflow can be exported as a versioned JSON document and imported again as a private draft. Import checks the graph against the same rules as deploy and lists up to 50 of the issues it finds, and personal account ids are stripped on export. See [Workflow export format](/developers/workflow-export-format).

### Connectors

For the systems most businesses run — accounting, payments, CRM, support, email, calendars, files and developer tools — use a built-in [connector](/integrations/catalog) rather than building your own.

## What does not exist yet

| You might expect | Status today | Use instead |
| - | - | - |
| Customer REST API with API keys | Not available | Incoming webhooks, public forms, MCP |
| Outgoing webhooks (Hive calls your URL on events) | Not available | A workflow step that acts through a connector, such as posting to Slack |
| Webhook-triggered workflows | Not available | A **Public form** trigger, which accepts an HTTP submission |
| A Hive MCP server | Not available | — |
| Email or push notifications | Not available | The in-app notification bell, and the Slack and Teams channels for questions |

## Limits at a glance

| Surface | Key limits |
| - | - |
| Incoming webhooks | 64 KB body, signed with HMAC-SHA256, deduplicated per webhook |
| Public forms | 20 requests/minute per form, 60/minute per IP, 64 KiB body |
| Workflows | 50 steps, 100 connections, 500 run steps per run |

The complete list is in [Limits reference](/developers/limits-reference).

## Related

<CardGroup cols={2}>
  <Card title="How Hive works" icon="diagram-project" href="/developers/how-hive-works">
    The architecture behind these surfaces.
  </Card>

  <Card title="Webhook signing" icon="signature" href="/developers/webhook-signing">
    Code samples for signed webhooks.
  </Card>

  <Card title="Security overview" icon="lock" href="/security/overview">
    How Hive keeps integrations safe.
  </Card>

  <Card title="Integrations overview" icon="plug" href="/integrations/overview">
    Every way to connect a tool.
  </Card>
</CardGroup>