ChatGPT
- Protocol
- GPT Actions
- Endpoint
- https://app.replynodes.com/api/public/v1
- Authentication
- Raw API key in Authorization (no Bearer), or pos_ OAuth app token
- Setup
- ChatGPT setup →
Social media API for AI agents
The ReplyNodes public API lets AI agents and applications schedule, publish, and manage social content programmatically — with social-account connections and support for integrations.
ReplyNodes is social media infrastructure for AI agents and applications. The public REST API at https://app.replynodes.com/api/public/v1 exposes the same publishing capabilities as the MCP server, for direct HTTP integration from any application.
Check verified OpenAPI publication status → The contract remains unpublished until the owning backend can export complete authoritative schemas.
Technical details: integration evidence
ChatGPT uses GPT Actions calling the REST API. It is not an MCP client. MCP clients use the remote MCP server. API keys are created in the app at Developers → API Keys & Agents (/developers).
Claude, Claude Code, Cursor, Codex, OpenClaw, Hermes
- Protocol
- Remote MCP
- Endpoint
- https://app.replynodes.com/api/mcp
- Authentication
- Authorization: Bearer *** key, or MCP OAuth
- Setup
- MCP setup →
Applications and workflow tools
- Protocol
- REST API
- Endpoint
- https://app.replynodes.com/api/public/v1
- Authentication
- Raw API key in Authorization (no Bearer), or pos_ OAuth app token
- Setup
- REST API setup →
How it works
1
Connect channels via OAuth2
Connect your social accounts to ReplyNodes once; the API then reads and publishes to them through the platform's integrations.
2
Authenticate your application
Send a raw API key in the Authorization header, or use an OAuth app token prefixed with pos_.
3
Schedule and publish
Create and schedule posts, check channel status, and follow the documented workflow.
What the API supports
Programmatic social-account connections
Connect and manage social accounts through the platform's integration layer.
Post scheduling and publishing
Create, read, update, and delete posts programmatically — draft, schedule, and publish across any connected channel.
Channel management
Add and remove connected social channels and check their connection status through the API.
Integrations
The same integration layer that powers the MCP server — one API connection covers publishing across the social networks you connect.
Workflow guidance
Consult the public API documentation for current supported workflows.
Security and authentication
API requests use a raw API key in the Authorization header, with no Bearer prefix. OAuth app tokens prefixed with pos_ work identically. Create API keys at Developers → API Keys & Agents (/developers).
Frequently asked questions
How do AI agents authenticate with the ReplyNodes API?
Use a raw API key in the Authorization header, or use an OAuth app token prefixed with pos_. Both work with the public API; API keys are created at Developers → API Keys & Agents (/developers).
Can the API schedule posts ahead of time?
Yes — the API supports creating and scheduling posts programmatically, the same way the MCP server does. Agents can queue posts with specific timing and content for any connected channel.
Where can I find API workflow guidance?
Use the public API documentation for current endpoint, authentication, and workflow guidance.
What can agents do through the public API?
Agents and applications can connect social accounts via OAuth2, create and schedule posts, publish across every connected channel, and manage channel connections — through the same integration layer that powers the MCP server.
What's the difference between the API and the MCP server?
Both give agents programmatic access to the same publishing capabilities. MCP is a tool interface for AI agents that use the Model Context Protocol; the REST API is for direct HTTP integration from any application, script, or workflow tool.
Get started: read the public API docs, see the OAuth2 flow, or use the social media MCP server for AI agents, or Open ReplyNodes.