Developer platform

Build with
the hive.

Connect a trusted server or AI client to one social workspace—without bypassing roles, plan limits, provider permissions, human approval, or Hive's protected controls.

MCP endpointhttps://hivepublish.com/api/mcp
Three interfaces

Different clients.
One safety boundary.

Use only the interface your product needs. The underlying authority does not change.

Workspace API

Keys and OAuth stay scoped.

Create an expiring server key in Settings → API or let a compatible MCP client use OAuth 2.1, PKCE, and dynamic client registration. Every credential stays bound to one workspace.

Authorization: Bearer hive_…
REST and MCP

One permission engine.

The Streamable HTTP MCP endpoint, versioned REST tools, OpenAPI document, and Hive Assistant resolve the same tool definitions, scopes, roles, plans, and approvals.

POST /api/v1/tools/create_draft
Events

Signed, bounded notifications.

Owner and admin credentials can subscribe to supported change events. Hive signs the exact body, retries bounded failures, and never turns webhooks into a second private-data export API.

X-Hive-Signature: v1=<hmac>
Marketplace and partner program

Distribution—not a pile of API keys.

A creator Marketplace is the discovery layer for embedded experiences and connected apps: social feeds, forms, bookings, maps, commerce, audience sync, media, and other tools a creator can add to a public page. The developer program is the separate partner path used to build, review, support, and eventually distribute those experiences.

Hive's current public API serves workspace automation. The Link in Bio app catalog is a creator product surface. A third-party Marketplace submission flow remains a gated partner program and is not represented as open or self-service until its review operations and production backend exist.

Explore Hive integrations
Partner lifecycle

A listing is earned
through review.

These are the required checkpoints. Public Marketplace submissions are not open yet.

  1. 01

    Register interest

    Share the product, customer value, data handling, requested permissions, and support owner. Hive is not presenting an open self-serve submission form yet.

  2. 02

    Design review

    Define the Link in Bio experience, authorization boundary, consent copy, failure states, privacy policy, and provider-specific limits before implementation.

  3. 03

    Sandbox validation

    Exercise install, disconnect, token expiry, empty data, rate limits, accessibility, webhooks, and every nested setting without writing to customer workspaces.

  4. 04

    Listing review

    Review listing art and copy, category, support contact, security evidence, demo workspace, uninstall behavior, and truthful plan requirements.

  5. 05

    Monitored release

    Publish only after approval, start with a bounded audience, observe errors and delivery, and retain a revocation path. No source change claims this gate is complete.

Partner intake is deliberately fail-closed.No inert form, fake confirmation, automatic listing, or implied approval is exposed.
TypeScript SDK

Built and packed.
Not falsely published.

@hive-social/sdk contains a typed client, REST tool calls, webhook management, structured errors, MCP configuration, and constant-time webhook verification. It is built, tarball-inspected, and clean-install tested from source.

A repository package is not an npm release. Hive only advertises registry installation after the exact version passes a live npm view and clean external install check.

Source package · Node 18+
import {
  HiveClient,
  verifyHiveWebhookSignature,
} from '@hive-social/sdk';

const hive = new HiveClient({
  accessToken: process.env.HIVE_ACCESS_TOKEN,
});

const tools = await hive.listTools();
Capability contract

39 tools.
Each one scoped.

The connected workspace, member role, plan, credential scopes, and confirmation policy are authoritative.

Read scopes
  • read:product
  • read:channels
  • read:calendar
  • read:content
  • read:analytics
  • read:reports
  • read:campaigns
  • read:inbox
  • read:community
  • read:listening
  • read:automations
  • read:podcasts
  • read:portfolio
  • read:jobs
Opt-in write scopes
  • write:ideas
  • write:drafts
  • write:campaigns
  • write:reports
  • write:schedules
  • write:content
  • write:community
  • write:automations
  • write:podcasts
  • write:publishing
  • admin:workflow
Explore all 39 tool definitions
read_product_knowledge

Explain Hive screens, metric semantics, capabilities, limitations, and organic-only rules.

read:product
read_channels

List connected organic channels and their connection health. No tokens or secrets are returned.

read:channels
read_calendar

Read scheduled, draft, approval, failed and recently published workflow items.

read:calendar
read_posts

Read public canonical post history for evidence, pattern analysis, and repurposing. Date filters apply to the native publication time.

read:analytics
read_analytics_summary

Read latest organic account and post metrics while retaining native fields and metric availability.

read:analytics
read_reports

List saved report definitions and delivery-safe metadata.

read:reports
read_campaigns_and_tags

List campaigns and internal post tags.

read:campaigns
read_best_times

Read configured posting schedules and recent post timing evidence. Recommendations must disclose their basis.

read:analytics
read_inbox_summary

Read aggregate inbox status counts only. Never returns DMs, message bodies, contact PII, or private records.

read:inbox
read_listening

Read saved listening queries, provider coverage, and aggregate snapshot metrics.

read:listening
read_approval_workflows

Read approval workflow definitions and recent approval runs.

read:content
read_report_schedules

Read configured report delivery schedules without exposing recipient addresses.

read:reports
read_competitors

Read tracked public competitors and stored official-provider snapshots.

read:analytics
read_automations

Read comment and DM automation configuration, state, and aggregate results.

read:automations
read_advocacy

Read employee-advocacy content and approval state.

read:content
read_podcasts

Read podcast shows, episodes, RSS metadata, and distribution state without owner contact details.

read:podcasts
read_reviews

Read review operations and assignment state. Provider-live review bodies and reviewer identities remain excluded.

read:community
read_portfolio

List the connected user's permitted Hive workspaces for Queen multi-brand routing.

read:portfolio
read_jobs

Read recent asynchronous developer jobs and their progress.

read:jobs
read_inbox_threads

Read owner-enabled, redacted Inbox threads. Defaults to unavailable; raw contacts, private notes, secrets, and unredacted bodies are never returned.

read:community
read_content_page

Read an opaque cursor-paginated page of posts, ideas, or campaigns without changing the legacy list tools.

read:content
read_job_page

Read an opaque cursor-paginated page of asynchronous developer jobs.

read:jobs
create_idea

Create an idea in the workspace content board.

write:ideas
create_draft

Create an editable organic post draft. This never publishes.

write:drafts
create_campaign

Create an organic workspace campaign.

write:campaigns
create_report

Create a saved analytics report from an existing Hive template.

write:reports
schedule_post

Schedule an existing draft or new post. A human must approve the exact action in Hive first; immediate publishing is a separate protected workflow.

write:schedules · human approval
update_draft

Update the title, caption, hashtags, or channels of an existing draft. Never publishes.

write:content
create_tag

Create an internal workspace content tag.

write:content
create_saved_reply

Create an internal saved reply. This does not send it to anyone.

write:community
add_competitor

Resolve a public competitor through an official provider API and store the first snapshot.

write:content
create_podcast_show

Create a draft podcast RSS show. This does not submit it to Apple, Spotify, or YouTube.

write:podcasts
reschedule_post

Move an existing draft, scheduled, or failed post to a future time after a human approves the exact change.

write:publishing · human approval
cancel_scheduled_post

Return a scheduled or approval-pending post to drafts after a human approves the exact change.

write:publishing · human approval
pause_automation

Pause an active or scheduled customer-facing automation and skip its pending outbound actions.

write:automations · human approval
queue_competitor_refresh

Queue a provider-backed refresh for all or selected tracked competitors and return an asynchronous job ID.

write:content
cancel_job

Request cancellation of a queued or running asynchronous job created by this API connection.

write:content
reply_to_comment

Post a public reply to an existing Hive Inbox comment after a human approves the exact thread and text.

write:community · human approval
send_direct_message

Send a direct message through a connected provider after a human approves the exact recipient and text.

write:community · human approval
Workspace quotas

Explicit limits.
No surprise multiplication.

No active plan1 API key3,000 requests / month
Worker Bee3 API keys7,500 requests / month
Swarm5 API keys15,000 requests / month
Queen Bee10 API keys50,000 requests / month

The request allowance is shared by the workspace. More keys do not create more quota.

Versioned REST

A draft request
stays a draft.

curl -X POST https://hivepublish.com/api/v1/tools/create_draft \
  -H "Authorization: Bearer hive_…" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: campaign-42-draft-1" \
  -d '{"caption":"Launch day","channelIds":["CHANNEL_UUID"]}'
Production evidence

Local green is not live green.

  • Apply and replay the versioned developer migrations in the selected production project.
  • Deploy the canonical domain and probe REST, OpenAPI, MCP discovery, OAuth metadata, DCR, consent, and revocation.
  • Complete a real client OAuth flow and a scoped-key flow against a non-customer workspace.
  • Verify approval replay protection, webhook delivery/retry, quota exhaustion, audits, and fail-closed denial paths.
  • Publish an approved SDK version, then prove registry metadata and a clean external install.
  • Staff partner intake, security/privacy review, listing moderation, support, revocation, and monitored rollout before opening submissions.