Copyjump LogoCopyjump Logo
REST API for SEO content creation

Create and publish SEO content with the CopyJump API

Use the REST API to create Content Tasks, schedule the CopyJump agent, fetch finished SEO drafts, and move approved content into your CMS, app, or internal workflow.

Set Up APISee The MCP Server

CopyJump writes the SEO draft. Your system decides where it goes next.

The REST API is the bridge between CopyJump and the tools your team already uses to plan, approve, publish, and track content. You keep your CMS, planning board, and approval process, and CopyJump stays the research and production engine behind them.

It fits the work systems usually do: create Content Tasks from briefs, campaigns, or records in your own planning system, schedule the agent when a task is ready, then fetch the finished markdown and metadata and mark it synced once your stack has published it. That covers CMS sync into WordPress, Next.js, or a headless CMS, agency delivery workflows, and internal automation.

Need an assistant-driven workflow instead? See the MCP server
How teams use it

Automate the content flow around CopyJump.

REST works best when CopyJump is one step in a larger pipeline. Planning happens in your system, CopyJump writes the draft, and your stack publishes the result. Four steps, start to finish.

  1. 1

    Send the work in

    Your system creates a Content Task from a brief, campaign, or planned idea.

  2. 2

    Run the agent

    CopyJump writes the SEO draft with brand and keyword context already attached.

  3. 3

    Pull the finished draft

    Your CMS or app fetches the approved markdown and metadata when it is ready.

  4. 4

    Keep status accurate

    Mark the content synced, archived, or published once your system has handled it.

Publishing stack

One step in a larger content pipeline.

The API moves work into CopyJump and moves finished SEO content back out, so the rest of your pipeline does not change. You can send planned work in from a calendar, CRM, Airtable base, or Notion board so SEO starts where your team already plans campaigns, bring approved drafts back out when your CMS or content repo is ready to import and run final checks, and keep status aligned by updating synced and archived state after the piece is handled.

Current V1 surface

REST API endpoints

The current REST surface focuses on the objects external systems need most: finished content, Content Tasks, and agent scheduling.

MethodPathUse
Content
GET/content

List content records without body content.

GET/content/{id}

Fetch one content record, including markdown body.

PATCH/content/{id}

Update supported content state fields.

Content tasks
GET/content-tasks

List content task planning records.

POST/content-tasks

Create a content task from an external idea or brief.

GET/content-tasks/{id}

Fetch one content task and its current derived state.

PATCH/content-tasks/{id}

Update supported task fields.

Agent
POST/content-tasks/{id}/agent

Schedule or unschedule CopyJump agent work for a task.

Guide
GET/how-to-use

Fetch the current API guide for integrators and agents.

Connection

Simple brand-scoped API access.

Create one brand-scoped bearer API key for the brand you want to connect. The key sets the brand context, so your backend creates tasks, fetches finished drafts, and keeps publishing status in sync without passing brand or organization IDs. The base URL is https://app.copyjump.com/api/v1. Reach for the MCP server instead when an AI assistant needs to plan and act interactively in chat.

REST is for apps.

Use the API when a backend service, CMS connector, or internal system needs predictable HTTP calls.

Using an AI agent? See the MCP server.

MCP exposes the same product contract as agent-friendly tools for Claude, ChatGPT, Codex, and similar clients.

Explore MCP

Frequently Asked Questions

Is the REST API for normal app integrations or AI agents?▼

Use REST when you are building a backend integration, CMS sync, publishing pipeline, or internal tool. If an AI assistant needs to call CopyJump interactively, the MCP server is the better surface.

How does authentication work?▼

REST uses brand-scoped API keys passed as bearer tokens. The key selects the brand context, so external REST callers do not pass brand or organization IDs.

Can I write directly to content bodies?▼

V1 content updates are intentionally narrow and focus on state such as status, synced, and archived. Full body writes are a separate workflow and should not be assumed.

Can I use this with WordPress, Next.js, or a headless CMS?▼

Yes. CopyJump provides the content and workflow state. Your integration decides how to transform markdown, map metadata, and publish into the final system.

Set up the CopyJump API for your publishing workflow.

Create Content Tasks, run the agent, and pull finished SEO drafts straight into your CMS, app, or internal tools.

See the MCP server

Brand-scoped API keys. REST for systems, MCP for AI assistants.