canonical: https://jentic.com/apis/hivepublish.com/hivepublish # Hive Publish Developer API The Hive Publish Developer API automates organic social messaging and publishing: it drafts and schedules posts to twelve networks, answers direct messages on Instagram, Messenger, WhatsApp, and Telegram from one inbox, runs comment and DM automations, and reports on performance. Hundreds of operations span content, inbox, contacts, automations, listening, and reporting for a single workspace. Use it to run an organic social presence from an agent or app instead of logging into each network by hand. ## For AI agents Draft and schedule social posts, answer DMs and comments from one inbox, run automations, manage contacts, and read cross-network analytics for a workspace. ## Scope Does not run paid ad campaigns, process payments, or host your website. Use for organic social publishing, inbox management, automations, and reporting only. ## Capabilities - Draft, schedule, and publish posts across the connected social networks - Send direct messages and reply to comments from the Community inbox - Read, assign, and resolve inbox conversations with tags and notes - Create contacts and set their tags and stored field values - Build comment and DM automations and set them live or on pause - Read cross-network analytics summaries and saved reports - Register signed webhook subscriptions for workspace events ## Use cases ### Scheduled Cross-Network Publishing Queue content once and let Hive Publish deliver it to each connected network at the chosen time, instead of posting to Instagram, Telegram, and the rest separately. The API creates an editable draft with the composer options, then schedules it for a future slot in the workspace queue. Social teams use this to run a consistent posting calendar across a dozen networks from one place. Example prompt: POST `/api/v1/tools/create_draft` with the post content and target accounts, then POST `/api/v1/tools/schedule_post` to queue it for a future time. ### Unified Social Inbox Triage Work every incoming DM and comment from one inbox and close them with a recorded resolution reason, rather than switching between native apps. The API lists redacted inbox threads, assigns them to teammates, and resolves them with a reason from the workspace's configured list. Support and community teams use this to keep response times low across channels. Example prompt: POST `/api/v1/tools/read_inbox_threads` to list open conversations, then POST `/api/v1/tools/resolve_thread` with a resolution reason for each handled thread. ### Contact Tagging and Segmentation Keep the contact records Hive Publish builds from DM automation organized so segments and reporting stay accurate. The API finds a contact by email, phone, or a field value and lets you add tags or set stored field values by id or name. Marketing teams use this to label contacts for later broadcasts and sequences. Example prompt: Call GET `/api/v1/contacts` to find a contact by email, then POST `/api/v1/contacts/{id}/tags` to add a tag by name. ### Agent-Managed Social Workflow An AI agent prepares and queues social content for a workspace without a bespoke integration against each network. Through Jentic the agent discovers the draft and schedule operations, loads their schemas, and chains them, then reports the resulting queue entry. This lets a marketing assistant turn a brief into scheduled posts directly. Example prompt: Search Jentic for 'schedule a social post', draft with POST `/api/v1/tools/create_draft`, schedule with POST `/api/v1/tools/schedule_post`, and return the queued entry. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/api/v1/tools/create_draft` | Create an editable post draft | | POST | `/api/v1/tools/schedule_post` | Queue a post for a future time | | POST | `/api/v1/tools/send_direct_message` | Send a direct message from a connected account | | POST | `/api/v1/tools/read_inbox_threads` | Read redacted inbox conversation threads | | POST | `/api/v1/tools/read_analytics_summary` | Read the latest organic metrics per account | | GET | `/api/v1/contacts` | Find contacts by email, phone, or field value | | POST | `/api/v1/contacts/{id}/tags` | Add a tag to a contact by id or name | | POST | `/api/v1/webhooks` | Create a signed webhook subscription | ## Key resources - **Posts and Scheduling** — Create drafts, schedule posts, reschedule or cancel them, and read the publishing queue - **Inbox and Messaging** — Read inbox threads, send direct messages, reply to comments, assign and resolve conversations - **Contacts** — Find, create, tag, and update contacts and their stored field values - **Automations** — Create comment and DM automations, set them live or paused, and read their results - **Analytics and Reports** — Read analytics summaries, saved reports, benchmarks, and listening data - **Webhooks** — List, create, and disable signed developer webhook subscriptions ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 52 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 48 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 51 / 100 - Agent Usability: 43 / 100 - Security: 60 / 100 - AI Discoverability: 58 / 100 - **View full report:** https://jentic.com/apis/hivepublish.com/hivepublish/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring Hive Publish by hand means handling its bearer auth and picking the right operations out of a very large surface for drafting, scheduling, inbox, and automations. Through Jentic you install once, import Hive Publish from the API Directory, store the token once, and your agent calls the operation it needs. - **Permission scoping:** Hive Publish carries post content, channels, and message targets inside the request body, so a rule bounds which operations your agent may call rather than which account or channel. You can allow only read and draft operations and withhold the ones that publish, send messages, or set automations live. - **Credential handling:** Your Hive Publish bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'schedule a social post' or 'read the social inbox', and Jentic returns the matching Hive Publish operation with its input schema so the agent calls the right endpoint without browsing hundreds of tools. ## Related APIs - **Buffer API** — Scheduling and publishing across social networks - **Sprout Social API** — Publishing, inbox, and social listening in one suite - **Phyllo API** — Creator and audience data from connected social accounts ## FAQ ### Is there a Hive Publish MCP server? Yes. Hive Publish offers an MCP server that exposes its organic-social tools. You can also connect Hive Publish directly through Jentic: your agent gets the full 258-endpoint surface without loading another server's tool definitions into its context, your bearer token is injected at call time by your self-hosted instance instead of living in a config file, and your own rules decide which operations the agent may call. ### What authentication does the Hive Publish Developer API use? The Hive Publish Developer API authenticates with a bearer token in the Authorization header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt, logs, or context. ### Can I manage the social inbox with the Hive Publish Developer API? Yes. POST `/api/v1/tools/read_inbox_threads` returns redacted conversation threads, POST `/api/v1/tools/assign_thread` hands one to a teammate, and POST `/api/v1/tools/resolve_thread` closes it with a resolution reason. Direct messages are sent with POST `/api/v1/tools/send_direct_message` on a connected account. ### What are the rate limits for the Hive Publish Developer API? The OpenAPI spec does not specify request rate limits; Hive Publish meters usage per connected account on its pricing tiers. Check the Hive Publish documentation at https://hivepublish.com for the current limits that apply to your plan. ### How do I schedule a social post through Jentic? Search Jentic with the query 'schedule a social post', load the schema for POST `/api/v1/tools/create_draft`, create the draft, then execute POST `/api/v1/tools/schedule_post` to queue it. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with the Hive Publish Developer API? Yes. Write a rule that allows only the read and draft operations, such as reading the inbox and creating a draft, so the agent can prepare content and report back without publishing or messaging anyone, and every call it makes is logged. Granting the schedule, send, or automation operations is an explicit choice you add.