> ## Documentation Index > Fetch the complete documentation index at: https://docs.groniz.com/llms.txt > Use this file to discover all available pages before exploring further. # API Overview > Getting started with the Groniz Public API ## Clients & Integrations The API is plain HTTP + JSON, so any language works with a bare request. Two first-party clients wrap it for you: Drive the API from your terminal or a coding agent — `curl -fsSL https://groniz.com/install.sh | sh` Expose Groniz as tools to any MCP client (Claude, Cursor, …) at `https://mcp.groniz.com/mcp` ## Authentication There are two ways to authenticate with the Groniz API: ### API Key Get your API key from **Settings > Developers > Public API**. Include it in the `Authorization` header: ```bash theme={null} curl -H "Authorization: your-api-key" https://api.groniz.com/public/v1/integrations ``` ### OAuth2 Token If you're building an app for other Groniz users, use [OAuth2 Authentication](/public-api/oauth) to get tokens that act on behalf of users. OAuth tokens start with `pos_` and are used the same way: ```bash theme={null} curl -H "Authorization: pos_your-oauth-token" https://api.groniz.com/public/v1/integrations ``` ## Base URL All requests go to: ``` https://api.groniz.com/public/v1 ``` ## Rate Limits **90 requests per hour** (100 for the cloud) limit applies to only the create post endpoint. This doesn't mean you can only post 90 times per hour—each API call counts as one request. Schedule multiple posts in a single request to maximize throughput. The rate limit is a single global value — it doesn't tier by subscription plan. Plans tier on channel and post-per-month quotas instead. ## Errors | Status | Meaning | | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `400 Bad Request` | The request body or path parameter is malformed (wrong shape, unknown enum, missing required field). | | `401 Unauthorized` | `Authorization` header is missing or the API key is unrecognised. | | `403 Forbidden` | The API key is valid but doesn't own the resource (e.g. you tried to delete a post in another organisation). | | `404 Not Found` | The endpoint doesn't exist, or the path parameter (integration ID, post ID) was correct format but no row matched. | | `413 Payload Too Large` | Your request body exceeded 50 MB on `/posts` — usually because images were base64-inlined instead of pre-uploaded. See [Uploads troubleshooting](/troubleshooting/uploads). | | `429 Too Many Requests` | You exceeded `API_LIMIT` per hour on the create-post endpoint. | | `5xx` | Server error — retry with exponential backoff. | For `DELETE` endpoints, `404` always means "already deleted" and is safe to ignore. A `500` *can* mean the same thing today because of a [known issue](/troubleshooting/known-issues) where a missing post ID surfaces as 500 instead of 404 — but only if the error matches that specific signature. Treat other `500` responses as real server errors: log them, retry with exponential backoff, and don't silently suppress them. ## Terminology The Groniz UI uses the term **channel**, while the API uses **integration**. They refer to the same thing—a connected social media account. ## Generate Output The easiest way to generate your post payloads is by using this wizard. It's the same wizard used to schedule posts in the Groniz app, but instead of scheduling, it generates the JSON payload for you to use in your API requests. Make sure you are signed in to the [console](https://groniz.com/console/connectors) first.