Nimply API & MCP
The social media API built for the AI era
Schedule, publish, and measure content across 9 platforms from your code, your automations, or your AI assistant. REST API, MCP server, and signed webhooks — included on every plan.
Free plan included · no separate API pricing
$ curl https://api.nimply.io/v1/posts \
-H "Authorization: Bearer nim_live_…" \
-d '{
"channelIds": ["…"],
"content": "Launch day 🚀",
"schedule": "next_slot"
}'
{ "status": "SCHEDULED", "scheduledAt": "2026-08-01T09:00Z" }Model Context Protocol
Your AI assistant becomes your social media manager
Connect Nimply's MCP server and ask your assistant to plan a week of posts, schedule them into the best time slots, and report what performed — in one conversation. Sixteen tools, permission-scoped, revocable anytime.
https://mcp.nimply.io/mcpAny MCP client works — OAuth for connectors, API keys for config files. Setup guides →No code required
Automate without writing a line
Pipe RSS feeds, spreadsheets, and forms into your posting queue — and get instant alerts the moment a post publishes or fails. Nimply's webhooks power real triggers, not polling.
- Zapier — triggers and actions for 6,000+ apps
- Make — instant-trigger modules and scenarios
- n8n — self-hosted node with full API coverage
Everything the app does, your code can do
A versioned REST API over the same engine that powers Nimply — with OAuth 2.1, granular scopes, idempotent retries, and problem+json errors.
POST /v1/postsPosts & scheduling
Create drafts, queue into each channel's next free slot, publish now, or schedule to the minute — one post per channel, carousels included.
POST /v1/posts/bulkBulk creation
Send up to 50 posts in one request with per-item results, built for CSV imports and RSS pipelines.
POST /v1/mediaMedia upload
Import from any public URL, or upload raw bytes through presigned URLs — stored, thumbnailed, ready to attach to posts.
POST /v1/webhooksSigned webhooks
Published, failed, approval events and more — HMAC-signed, retried with backoff. No polling.
GET /v1/analytics/…Analytics
Followers, engagement, reach, and per-post metrics across every channel, with date ranges.
POST /v1/posts/{id}/approveApproval workflow
Route drafts to clients for sign-off and record every decision — built for agencies.
Create a key
In Nimply, open Settings → Developers and create a scoped API key. Read-only by default.
Make your first call
GET /v1/channels lists your connected accounts — the five-minute quickstart takes you to a scheduled post.
Go live
Add webhooks for publish events, connect your AI assistant over MCP, or ship a Zap. Rate limits and retries are built in.
Frequently asked questions
Is the Nimply API included in my plan?
Yes. API access is included on every Nimply plan, including Free. Create a workspace API key under Settings → Developers and start calling the API immediately.
Does Nimply work with Claude, ChatGPT, and other AI assistants?
Yes. Nimply runs a remote MCP (Model Context Protocol) server at mcp.nimply.io. Add it as a connector in claude.ai or ChatGPT and approve access with a login — or configure it with an API key in Claude Code, Claude Desktop, Cursor, and any other MCP-capable client. The assistant can then list your channels, draft and schedule posts, and read your analytics conversationally.
Which social platforms can I publish to through the API?
Facebook (Pages and Groups), Instagram, X (Twitter), LinkedIn (profiles and pages), TikTok, YouTube, Pinterest, Threads, and Google Business Profile — the same channels you connect in the Nimply app.
Does the API support webhooks?
Yes. Register an HTTPS endpoint and Nimply pushes signed events — post published, post failed, approval requested, and more. Deliveries carry an HMAC-SHA256 signature, retry five times with backoff, and power instant triggers in Zapier, Make, and n8n.
How is the API authenticated?
Two ways: workspace-scoped API keys with granular permissions (read-only by default), or OAuth 2.1 with PKCE for connector-style apps. Every credential is scoped to one workspace, so client access stays cleanly separated.
Are there rate limits?
Yes — 60 requests per minute per API key, with standard X-RateLimit headers on every response so your integration can pace itself. Mutating endpoints also accept an Idempotency-Key header, making retries safe.
Ship your first post in five minutes
The quickstart walks from API key to a scheduled post — reference, guides, and per-client MCP setup included.