Overview

The XreplyAI Public API lets you programmatically schedule and publish posts, generate content with your trained voice, upload media, read your connected social accounts, and pull post analytics across X, LinkedIn, Instagram, Threads, Facebook, YouTube, TikTok, Pinterest, Bluesky, Mastodon, Discord, Telegram, Tumblr, Google Business, and Slack.

Quickstart

Your first scheduled post in five steps.

Authentication

Scoped API keys and how to use them.

API Reference

Every endpoint, generated from the OpenAPI spec.

MCP Server

Drive XreplyAI from Claude and other MCP clients.

Base URL

All endpoints live under:

https://api.xreplyai.com/api/v1

Requests and responses are JSON. Authenticate every request with a bearer API key; see Authentication.

Availability

The API is available on all paid plans (Starter, Pro, or Team). Create your key in the dashboard under Settings → API Keys.

Pagination

List endpoints that can grow (currently GET /posts) accept limit and offset query parameters and return a meta envelope:

{ "meta": { "limit": 100, "offset": 0, "total_count": 342 } }

limit defaults to 100 and is capped at 200; values above 200 are clamped. offset defaults to 0. Page by incrementing offset by your limit until offset + limit >= total_count.

Versioning

The API is versioned in the path (/api/v1). Within v1 the contract is additive-only: fields are never removed or renamed. Breaking changes ship under a future /api/v2.

The spec is the contract

The OpenAPI 3.1 spec is the machine-readable source of truth. The API Reference section of this site is generated from it on every build.