Support
How to get help with the SociaHive API, SDKs, MCP server, or any of the integrations.
Pick the channel that fits the kind of question you have.
Product questions
Pricing, billing, account access, custom integrations — anything not strictly developer-facing.
SDK / API issues
Open an issue on the repo that matches the surface — sociahive-node, sociahive-python, cookbook, or zapier-platform-app.
MCP integration
Re-check the setup guide first — the troubleshooting section covers the most common failures.
Choose the right repo for an issue
| Symptom | Repo |
|---|---|
Bug in @sociahive/sdk (typed wrong, throws unexpectedly, etc.) | sociahive/sociahive-node |
Bug in sociahive PyPI package | sociahive/sociahive-python |
| Cookbook recipe doesn't run / produces wrong output | sociahive/cookbook |
| Zapier app feature request / submission feedback | sociahive/zapier-platform-app |
| Docs typo, broken link, missing topic | Same as above — open on whichever repo the docs sit closest to. For the docs site itself, email us. |
| The REST API returned an unexpected error | Email with the response body and details.request_id value |
What to include in a bug report
For SDK / API bugs, the following speeds up triage substantially:
- What you ran — full command or code snippet, with the API key redacted
- What you expected — one or two sentences
- What happened — full error message, including the
codeand HTTP status if applicable. Includedetails.request_idfrom the response — it lets us find the corresponding server log - Environment — SDK version, Node / Python version, OS
Status
Live status of the production API isn't on a public statuspage yet. If multiple consumers are reporting the same outage at the same time, expect an email update from [email protected].
Security
For security-sensitive issues — auth bypass, token leakage, signature verification flaws — don't open a public GitHub issue. Email [email protected] with SECURITY in the subject line and we'll respond with a private channel for the details.