Skip to content
API / MCP

REST API and an MCP server, on the entry plan and in the trial.

A public REST API and a Model Context Protocol server on every plan including the free trial, an OAuth 2.1 connector that puts the product inside Claude and ChatGPT, and HMAC-signed webhooks any script can consume.

  • 14-day trial, no card
  • Included on every plan

Why it works this way

Most platforms treat the API as the thing you buy the top plan for. Ours is on the cheapest paid tier and in the free trial, and the reason is written into the code: the flag that controls it is annotated as the competitive wedge and is set on all five plans. Automation is the point, not the upsell.

The REST API covers the product surface — create and schedule posts, upload media through presigned URLs, generate text, images and video, read analytics, work the inbox, resolve the next free slot. Every route is described once in a typed table that also generates the OpenAPI document, so the reference cannot drift from the handlers. Keys are hashed at rest, workspace-scoped and permission-scoped, with their own rate limits, last-used timestamps and instant revocation — and the scope vocabulary is shared with OAuth, so there is no second permission system to learn.

Every webhook carries an `x-gongong-signature` header: an HMAC over the timestamp and the exact bytes we sent, compared in constant time, inside a replay window. During a rotation we accept both the old and the new secret, so you can roll a key without dropping a delivery. Retries are logged and you can replay one from the delivery log.

The MCP server exposes the same capabilities as tools, running the same prompts, the same voice loading and the same post-processing as the web app — which is what lets an assistant genuinely run an account rather than approximate one. Add Gongong to Claude or ChatGPT as a custom connector and you get a hosted consent screen rather than a pasted API key: OAuth 2.1 with PKCE, dynamic client registration, single-use authorization codes, rotating refresh tokens with reuse detection, and a live membership check on every call, so revoking someone’s seat denies them immediately. Directory listings are in review; today you add it as a custom connector.

API / MCP

REST API and an MCP server, on the entry plan and in the trial.

A public REST API and a Model Context Protocol server on every plan including the free trial, an OAuth 2.1 connector that puts the product inside Claude and ChatGPT, and HMAC-signed webhooks any script can consume.

  • REST API v1 for generation, media, scheduling, publishing, analytics and the inbox — on Starter, the cheapest paid plan, and during the 14-day trial
  • Eleven MCP tools, so an assistant can draft, schedule, check analytics and answer a comment inside a surface you already have open
  • Every write accepts an Idempotency-Key and replays the stored response for 24 hours, so an agent that retries after a timeout cannot double-post

What you get

Inside api & mcp

The specifics, without the marketing adjectives.
  • Scoped API keys

    Hashed at rest, workspace-scoped, permission-scoped, with per-key rate limits, last-used timestamps and instant revocation.

  • Idempotent writes

    Every write route accepts `Idempotency-Key` and replays the stored response for 24 hours.

  • Signed webhooks

    post.published, post.failed, comment.received, dm.received, approval.requested, analytics.weekly_ready and more. Each is signed with an HMAC over the timestamp and the exact bytes sent, compared in constant time inside a replay window. Parse the header as a list of signatures and a future overlap needs no change on your side; a rotation today switches immediately, so deploy the new secret first.

  • MCP tools

    create_post, generate_content, repurpose_source, schedule_post, next_free_slot, get_analytics, list_accounts, reply_to_comment.

  • Connect it to Claude or ChatGPT

    An OAuth 2.1 authorization layer with PKCE, dynamic client registration and rotating refresh tokens, so an MCP client connects through a hosted consent screen instead of a pasted key. Add it as a custom connector — directory listings are in review, so we are not in one yet.

  • No-code paths too

    Connect through webhooks and the REST API: an HTTP call to /api/v1 with a scoped key, and a signed webhook pointed back at your listener. An n8n node, a Zapier app and a Make definition exist in beta, generated from the OpenAPI document so they cannot drift from the API — none of the three is in its vendor directory yet.

Keep going

Pairs well with

  • Repurposing engine

    Drop a YouTube link, a blog post, a PDF or an audio file. One run mines the distinct arguments inside it and expands each one into platform drafts, carousel copy, a short-video script and a Pin — all four delivered, each with one click through to the builder that finishes it.

    Read more
  • AI video studio

    Turn a script into a vertical video with AI voiceover, AI-generated scene visuals with motion, and animated captions — then edit it scene by scene and schedule it without leaving the workspace.

    Read more
  • Calendar & publishing

    Month, week, day and agenda views with drag-to-reschedule, queues and categories, evergreen recycling, and a publish pipeline built to a 99.5% success target, aiming to put a post live within 60 seconds of its slot.

    Read more

Try api & mcp on your own content

Fourteen days free, no credit card, and the public API is switched on from the first minute.

No credit card · Cancel anytime · Every plan includes the API and the MCP server