Groupilot Docs

Developers

Integrate Groupilot through the API, outbound webhooks, Connect OAuth and MCP.

Status

Reading, events, occurrences, communities, sequences (including PUT /v1/sequences/sync), pause and resume, media, sends, broadcasts, the member webhook, the backup admin, the account webhooks, Connect OAuth and the MCP server are published: the API reference and openapi.json describe them exactly.

What you can do

NeedUse
Push sequences written in your own platform into GroupilotPUT /v1/sequences/sync, see Sync your sequences
Create events for a client from your toolPOST /v1/events
React when someone joins a community, a message fails or a community fills upOutbound webhooks
Send a one-off message, edit, cancel or retry a planned sendSends
Message several communities at onceBroadcasts
Add a second admin number on the communities of an eventBackup admin by API
Let your users connect their Groupilot account with one clickConnect OAuth
Drive Groupilot from Claude or another AI assistantMCP
Glue it with no codeMake and n8n

The basics

  • Base URL: https://app.groupilot.com/api/v1
  • Auth: Authorization: Bearer gp_live_… (an API key) or an OAuth access token.
  • JSON in, JSON out. Errors are { "error": { "code", "message", "field?" } }.
  • One key is one project, which is one WhatsApp number.
  • Scopes: read, write (configure), send (send now). A key without send can prepare everything and send nothing.
  • Versioned under /v1. Breaking changes mean a /v2.

What the API never does

Create a project or a WhatsApp channel, show a QR code, change the number, delete or stop an event, add members to a community, send private messages, touch billing. Those stay in the app, with a human in front of the phone.

The full contract: openapi.json. The whole documentation in one file for an AI: llms-full.txt.

On this page