LxBlog/Docs
Dashboard

Getting Started

Introduction

Overview of the LxBlog API and what you can build

What is LxBlog?

LxBlog is an AI-powered blog automation platform that helps you create, manage, and distribute content at scale. The LxBlog API gives you programmatic access to your blog's content, enabling you to build integrations and sync articles to external platforms.

What can you build?

The API enables you to integrate LxBlog into your existing workflows and applications. Common use cases include:

  • Content syndication — Automatically publish articles to your website, CMS, or other platforms whenever new content is published.
  • Custom dashboards — Build internal tools that display article data alongside your other business metrics.
  • Static site generation — Fetch articles at build time to power a statically generated blog or documentation site.
  • Automated sync — Use the sync endpoint to efficiently detect and pull content changes into your application.

Key capabilities

  • OAuth 2.0 authentication — Secure authorization with support for PKCE, designed for both server-side and single-page applications.
  • Articles API — List, retrieve, and sync published articles with pagination. Content is delivered in Markdown format with SEO metadata, Schema.org structured data, and cover/inline images.
  • Diff-based sync — Efficient sync endpoint that compares content hashes and returns only new, updated, and deleted articles.
  • MCP server — Built-in Model Context Protocol server so AI assistants like Claude and Cursor can interact with your blog content directly.

Base URLs

All API requests are made to the following base URLs:

# REST API
https://lxblog.app/api/v1

# OAuth endpoints
https://lxblog.app/api/oauth

# MCP server (Model Context Protocol)
https://lxblog.app/api/mcp

All API requests must be made over HTTPS. Requests made over plain HTTP will be rejected.

Authentication overview

LxBlog uses OAuth 2.0 Authorization Code flow with optional PKCE support. After a user authorizes your application, you receive an access token that authenticates API requests on their behalf.

  • Access tokens expire after 1 hour and are used to authenticate API requests.
  • Refresh tokens expire after 30 days and are used to obtain new access tokens. Refresh token rotation is mandatory — each refresh request returns a new refresh token and invalidates the previous one.
Example request
curl https://lxblog.app/api/v1/articles \
  -H "Authorization: Bearer lxb_at_your_access_token"

Rate limiting

Standard rate limits apply to all API endpoints to ensure fair usage and platform stability. If you exceed the rate limit, the API will return a 429 Too Many Requests response. Retry after the duration indicated in the Retry-After header.

Use the sync endpoint instead of polling individual articles. It efficiently compares content hashes and returns only changes since your last sync.

Quick links

  • Quick Start — Get up and running with your first API call in minutes.
  • API Reference — Detailed documentation for every endpoint, parameter, and response.
  • Authentication — Deep dive into the OAuth 2.0 flow, scopes, and token management.
  • MCP Server — Connect AI assistants to your blog via the Model Context Protocol.
Next
Authentication