API Documentation

Use the SaveMySEO REST API to fetch AI-generated content and publish it to your platform. Articles are written and scheduled automatically — the API is how you retrieve them and sync publish status.

Authentication

All API requests require a Bearer token. Create an API key from your API Keys page.

Authorization: Bearer sk_live_your_key_here

All responses return JSON. Successful responses use { "data": ... } and errors use { "error": "..." }.

Getting Started

Use the SaveMySEO API to manage your sites, retrieve content, and set up webhooks for notifications.

List your sites — Call GET /api/v1/sites to see your sites and grab the id for the site you want.
Fetch content — Call GET /api/v1/content?siteId=... to list content items for a site.
Set up a webhook — Register a webhook for the scheduled_article_ready event so you get notified when new content is ready, instead of polling.

Example — list sites and fetch content:

# 1. List your sites to get the site ID
curl -H "Authorization: Bearer sk_live_your_key" \
  https://savemyseo.com/api/v1/sites

# 2. Get content for that site
curl -H "Authorization: Bearer sk_live_your_key" \
  "https://savemyseo.com/api/v1/content?siteId=abc123"

# Tip: Register a webhook so you don't need to poll for new content:
#   POST /api/v1/webhooks  {"events": ["scheduled_article_ready"]}

Sites

GET/api/v1/sites

List all your sites.

curl -H "Authorization: Bearer sk_live_your_key" \
  https://savemyseo.com/api/v1/sites

Response:

{
  "data": [
    {
      "id": "abc123",
      "url": "https://example.com",
      "name": "My Site",
      "createdAt": "2026-01-15T00:00:00Z",
      "updatedAt": "2026-01-15T00:00:00Z"
    }
  ]
}

GET/api/v1/sites/:siteId

Get a single site by ID, including all settings.

curl -H "Authorization: Bearer sk_live_your_key" \
  https://savemyseo.com/api/v1/sites/abc123

PATCH/api/v1/sites/:siteId

Update site settings. All fields are optional — only provided fields are updated.

Parameter	Type	Description
autoPublish	boolean	Enable auto-publishing to connected WordPress/Shopify
publishStatus	string	"draft" or "publish" — default post status for auto-publish
language	string	Content language code (e.g. "en", "es", "fr")
blogPathPrefix	string	Blog URL prefix (e.g. "/blog")

curl -X PATCH \
  -H "Authorization: Bearer sk_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{"autoPublish": true, "publishStatus": "publish"}' \
  https://savemyseo.com/api/v1/sites/abc123

DELETE/api/v1/sites/:siteId

Delete a site and all its associated data (articles, audits, keywords, etc.).

curl -X DELETE \
  -H "Authorization: Bearer sk_live_your_key" \
  https://savemyseo.com/api/v1/sites/abc123

Webhooks

Register webhooks to get notified when articles are ready. Instead of polling the API, your server receives a push notification.

Available events

scheduled_article_ready

Fires daily when generated articles are scheduled for today. Includes the date and count so you can fetch articles for that day.

Example webhook payload:

{
  "event": "scheduled_article_ready",
  "timestamp": "2026-03-11T06:00:00Z",
  "data": {
    "siteId": "abc123",
    "date": "2026-03-11",
    "count": 2
  }
}

Webhook payloads are signed with HMAC-SHA256. Verify the X-SaveMySEO-Signature header against the payload using your webhook secret.

GET/api/v1/webhooks

List all registered webhooks.

curl -H "Authorization: Bearer sk_live_your_key" \
  https://savemyseo.com/api/v1/webhooks

POST/api/v1/webhooks

Register a new webhook. The response includes a secret for verifying webhook signatures — save it, as it won't be shown again.

Parameter	Type	Description
url	string	Required. The HTTPS URL to receive webhook events.
events	string[]	Required. Array of event names to subscribe to.

curl -X POST \
  -H "Authorization: Bearer sk_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://yoursite.com/webhook", "events": ["scheduled_article_ready"]}' \
  https://savemyseo.com/api/v1/webhooks

Response:

{
  "data": {
    "id": "wh_123",
    "url": "https://yoursite.com/webhook",
    "events": ["scheduled_article_ready"],
    "secret": "a1b2c3d4e5f6...",
    "active": true,
    "createdAt": "2026-03-11T00:00:00Z"
  }
}

PATCH/api/v1/webhooks/:webhookId

Update a webhook's URL, events, or active status.

Parameter	Type	Description
url	string	New webhook URL (must be HTTPS)
events	string[]	Updated list of events
active	boolean	Enable or disable the webhook

curl -X PATCH \
  -H "Authorization: Bearer sk_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{"active": false}' \
  https://savemyseo.com/api/v1/webhooks/wh_123

DELETE/api/v1/webhooks/:webhookId

Delete a webhook.

curl -X DELETE \
  -H "Authorization: Bearer sk_live_your_key" \
  https://savemyseo.com/api/v1/webhooks/wh_123

Content

Retrieve AI-generated content items for your sites.

GET/api/v1/content

List content items. Returns paginated results without the full body.

Parameter	Type	Description
siteId	string	Site ID (required)
contentType	string	Filter by content type (e.g. comparison, listicle, how-to)
status	string	Filter by status: planned, generating, generated, needs-review, scheduled, publishing, published, failed (default: generated)
date	string	Exact date filter (YYYY-MM-DD). Overrides dateFrom/dateTo.
dateFrom	string	Start of date range (YYYY-MM-DD)
dateTo	string	End of date range (YYYY-MM-DD)
page	number	Page number (default: 1)
limit	number	Results per page (default: 20, max: 100)

curl -H "Authorization: Bearer sk_live_your_key" \
  "https://savemyseo.com/api/v1/content?siteId=abc123"

GET/api/v1/content/:id

Get a single content item by ID. Returns the full body, schema markup, and quality data.

curl -H "Authorization: Bearer sk_live_your_key" \
  https://savemyseo.com/api/v1/content/abc123-def456

PATCH/api/v1/content/:id

Update a content item's status. Use this to mark content as published after posting it to your CMS.

Parameter	Type	Description
status	string	New status: published, scheduled, or needs-review (required)
platformPostId	string	External URL or ID where the content was published (optional)

curl -X PATCH -H "Authorization: Bearer sk_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{"status": "published", "platformPostId": "https://example.com/blog/my-post"}' \
  https://savemyseo.com/api/v1/content/abc123-def456

Error Codes

Status	Description
400	Bad request — invalid or missing parameters, or invalid status transition
401	Unauthorized — invalid or missing API key
403	Forbidden — no organization associated with this key, or subscription required
404	Not found — resource does not exist or does not belong to your organization
409	Conflict — resource already exists (e.g. duplicate rolling plan) or is already being processed
500	Internal server error — something went wrong on our end