Recommended: API token

How to connect Custom API with Uplift.

Use API tokens and public content endpoints to power a headless frontend, proprietary CMS, or a completely custom publishing bridge. This guide walks through the recommended auth method, what you need before setup, and the exact path to get Custom API publishing cleanly from Uplift.

Headless-friendly content deliveryPreserves SEO metadata fieldsFlexible for custom integrations

Before you start

Make sure the destination and website context are ready before you connect.

3 prerequisites

A selected website in Uplift

A server or plugin that can call the public blog endpoints

A secure place to store tokens if you are making server-side requests

All Integrations Start Free Trial View API Reference

Connection Snapshot

Custom API

API token

Steps

Highlights

Checks

Step 1

Open the Custom API tab in Website Integration.

Step 2

Create an API token for the current website.

Step 3

Use the list and detail blog endpoints to fetch publish-ready content.

Managed in product

Website Integration > Custom API

After signup, this integration lives in the dashboard setup flow for the currently selected website so you can connect, test, and manage publishing without losing business context.

Why teams use it

Built for custom platforms, agencies, and engineering teams with their own stack.

Create API tokens and consume the public blog endpoints when you need a custom plugin, headless frontend, or proprietary CMS bridge.

Headless-friendly content delivery

Preserves SEO metadata fields

Flexible for custom integrations

After signup

Connect it from the right dashboard surface

You will manage Custom API from Website Integration > Custom API after choosing the website you want to connect.

This is the best option when you are building your own CMS bridge or plugin.

Path-based tokens work for browser-origin requests, while Bearer tokens are better for server-side calls.

Setup Guide

Everything you need before and during the Custom API setup

Prerequisites

A selected website in Uplift
A server or plugin that can call the public blog endpoints
A secure place to store tokens if you are making server-side requests

How to connect

1Open the Custom API tab in Website Integration.
2Create an API token for the current website.
3Use the list and detail blog endpoints to fetch publish-ready content.
4Preserve the SEO and freshness metadata when publishing into the destination system.

Implementation notes

This is the best option when you are building your own CMS bridge or plugin.

Path-based tokens work for browser-origin requests, while Bearer tokens are better for server-side calls.

API Reference

Use Uplift as a content source for a custom publishing bridge

If you are building your own plugin, headless frontend, or CMS sync, the public blog API gives you publish-ready content and SEO metadata without rebuilding the content pipeline from scratch.

API Documentation

Use your token to power a custom blog plugin, headless frontend, or CMS sync. The public blog API returns SEO metadata, author profile URLs, freshness info, and article fields so another platform can publish content without losing the structured SEO payload.

Integration Notes:

All responses are in JSON format
Browser calls can use the token in the URL path. Server-side calls can use Authorization: Bearer YOUR_TOKEN.
API tokens are scoped to the currently selected website.
Preserve the returned SEO metadata when publishing into another CMS to avoid losing title, OG, and freshness fields.

Guide FAQ

Common questions before you connect Custom API

What is the recommended way to connect Custom API?

API token is the recommended setup for Custom API. This is the best option when you are building your own CMS bridge or plugin.

What do I need before connecting Custom API?

Before you start, make sure you have A selected website in Uplift, A server or plugin that can call the public blog endpoints, A secure place to store tokens if you are making server-side requests.