Calendone writes the articles. Your site, script or AI agent pulls the approved ones and tells Calendone where they went live. Works with any custom platform.
import os
import requests
res = requests.get(
"https://mapp.calendone.io/api/v1/websites/7/articles?status=approved",
headers={"Authorization": f"Bearer {os.environ['CALENDONE_TOKEN']}"},
)
data = res.json()
package main
import (
"encoding/json"
"net/http"
"os"
)
func main() {
req, _ := http.NewRequest("GET", "https://mapp.calendone.io/api/v1/websites/7/articles?status=approved", nil)
req.Header.Set("Authorization", "Bearer "+os.Getenv("CALENDONE_TOKEN"))
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
var data map[string]any
json.NewDecoder(res.Body).Decode(&data)
}
Get started
Add your site, plan your content in Calendone, then automate publishing with the API or MCP.
Add your site
Create a free account and add your website.
Plan content
Calendone plans topics and writes the articles.
Automate publishing
Create a token under Team → API & MCP and connect your site or agent.
Send the token as Authorization: Bearer YOUR_TOKEN. One token works for every website in your team, and it’s shown only once, so store it safely. Create a free account →
Publishing flow
Run this on a schedule (for example every hour) or let your agent do it.
1
GET/websites
Find your website id.
2
GET/websites/{id}/articles?status=approved
Find articles ready to publish.
3
GET/websites/{id}/articles/{article_id}
Get the full article: HTML, Markdown, meta tags, images.
4
Publish it on your site with its slug, meta title and description, body and featured image.
import os
import requests
res = requests.get(
"https://mapp.calendone.io/api/v1/me",
headers={"Authorization": f"Bearer {os.environ['CALENDONE_TOKEN']}"},
)
data = res.json()
package main
import (
"encoding/json"
"net/http"
"os"
)
func main() {
req, _ := http.NewRequest("GET", "https://mapp.calendone.io/api/v1/me", nil)
req.Header.Set("Authorization", "Bearer "+os.Getenv("CALENDONE_TOKEN"))
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
var data map[string]any
json.NewDecoder(res.Body).Decode(&data)
}
import os
import requests
res = requests.get(
"https://mapp.calendone.io/api/v1/websites",
headers={"Authorization": f"Bearer {os.environ['CALENDONE_TOKEN']}"},
)
data = res.json()
package main
import (
"encoding/json"
"net/http"
"os"
)
func main() {
req, _ := http.NewRequest("GET", "https://mapp.calendone.io/api/v1/websites", nil)
req.Header.Set("Authorization", "Bearer "+os.Getenv("CALENDONE_TOKEN"))
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
var data map[string]any
json.NewDecoder(res.Body).Decode(&data)
}
import os
import requests
res = requests.get(
"https://mapp.calendone.io/api/v1/websites/7/articles?status=approved",
headers={"Authorization": f"Bearer {os.environ['CALENDONE_TOKEN']}"},
)
data = res.json()
package main
import (
"encoding/json"
"net/http"
"os"
)
func main() {
req, _ := http.NewRequest("GET", "https://mapp.calendone.io/api/v1/websites/7/articles?status=approved", nil)
req.Header.Set("Authorization", "Bearer "+os.Getenv("CALENDONE_TOKEN"))
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
var data map[string]any
json.NewDecoder(res.Body).Decode(&data)
}
Response · 200
{
"data": [
{
"id": 412,
"website_id": 7,
"status": "approved",
"title": "How to choose running shoes for flat feet",
"slug": "how-to-choose-running-shoes-for-flat-feet",
"excerpt": "What actually matters when you have flat feet, and how to test a shoe before you buy it.",
"language": "en",
"primary_keyword": "running shoes for flat feet",
"planned_for": "2026-11-12",
"revision": 3,
"replaces_article_id": null,
"approved_at": "2026-11-09T08:12:44+00:00",
"created_at": "2026-11-08T21:03:10+00:00",
"updated_at": "2026-11-09T08:12:44+00:00",
"publication": null
}
],
"meta": {
"page": 1,
"per_page": 20,
"total": 1,
"last_page": 1
}
}
One article with everything you need to publish it: HTML and Markdown body, meta title and description, slug and image URLs. Images are hosted by Calendone; download them if your site serves its own.
import os
import requests
res = requests.get(
"https://mapp.calendone.io/api/v1/websites/7/articles/412",
headers={"Authorization": f"Bearer {os.environ['CALENDONE_TOKEN']}"},
)
data = res.json()
package main
import (
"encoding/json"
"net/http"
"os"
)
func main() {
req, _ := http.NewRequest("GET", "https://mapp.calendone.io/api/v1/websites/7/articles/412", nil)
req.Header.Set("Authorization", "Bearer "+os.Getenv("CALENDONE_TOKEN"))
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
var data map[string]any
json.NewDecoder(res.Body).Decode(&data)
}
Response · 200
{
"data": {
"id": 412,
"website_id": 7,
"status": "approved",
"title": "How to choose running shoes for flat feet",
"slug": "how-to-choose-running-shoes-for-flat-feet",
"excerpt": "What actually matters when you have flat feet, and how to test a shoe before you buy it.",
"language": "en",
"primary_keyword": "running shoes for flat feet",
"planned_for": "2026-11-12",
"revision": 3,
"replaces_article_id": null,
"approved_at": "2026-11-09T08:12:44+00:00",
"created_at": "2026-11-08T21:03:10+00:00",
"updated_at": "2026-11-09T08:12:44+00:00",
"publication": null,
"meta_title": "How to choose running shoes for flat feet",
"meta_description": "What actually matters when you have flat feet, and how to test a shoe before you buy it.",
"featured_image": {
"url": "https://calendone-io.s3.eu-north-1.amazonaws.com/website-content/7/412/cover.webp",
"alt": "Runner tying a stability shoe",
"width": 1536,
"height": 1024
},
"images": [
{
"url": "https://calendone-io.s3.eu-north-1.amazonaws.com/website-content/7/412/cover.webp",
"alt": "Runner tying a stability shoe",
"width": 1536,
"height": 1024
}
],
"content_markdown": "\n\nFlat feet don’t automatically need…\n\n## What support actually means\n…",
"content_html": "<p><img src=\"https://calendone-io.s3.eu-north-1.amazonaws.com/website-content/7/412/cover.webp\" alt=\"Runner tying a stability shoe\" /></p>\n<p>Flat feet don’t automatically need…</p>\n<h2>What support actually means</h2>\n<p>…</p>"
}
}
Tell Calendone an approved article is live and where. Calendone then tracks it and moves it to published. Calling it again updates the record, so retries are safe. Needs a token with write access.
Approved changes to existing pages (from “Improve this page” in Calendone): new title, meta description, sections, FAQ, text replacements. Each one targets an existing page by URL and remote_id. Update that page; never create a new one.
Parameter
In
Type
Description
status
query
string
approved (default, waiting to be applied), applied or all.
import os
import requests
res = requests.get(
"https://mapp.calendone.io/api/v1/websites/7/page-updates",
headers={"Authorization": f"Bearer {os.environ['CALENDONE_TOKEN']}"},
)
data = res.json()
package main
import (
"encoding/json"
"net/http"
"os"
)
func main() {
req, _ := http.NewRequest("GET", "https://mapp.calendone.io/api/v1/websites/7/page-updates", nil)
req.Header.Set("Authorization", "Bearer "+os.Getenv("CALENDONE_TOKEN"))
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
var data map[string]any
json.NewDecoder(res.Body).Decode(&data)
}
Response · 200
{
"data": [
{
"id": 58,
"website_id": 7,
"status": "approved",
"operation": "update",
"target": {
"url": "https://fitalert.com/blog/running-shoes-flat-feet",
"remote_id": "post_8812",
"page_type": "post"
},
"keyword": "running shoes for flat feet",
"revision": 2,
"base_fingerprint": "sha256:9b1c…",
"approved_at": "2026-11-19T10:04:12+00:00",
"applied_at": null,
"applied_revision": null,
"changes": [
{
"id": "c1",
"type": "title",
"anchor": "",
"before": "Running shoes for flat feet",
"after": "Best running shoes for flat feet (2026): how to choose"
},
{
"id": "c2",
"type": "meta_description",
"anchor": "",
"before": "",
"after": "What flat feet really need from a running shoe, how to test support in the shop, and five models runners with flat feet like."
},
{
"id": "c3",
"type": "faq",
"anchor": "How to test a shoe",
"before": "",
"after": "## FAQ\n\n### Do flat feet need stability shoes?\nNot always…"
},
{
"id": "c4",
"type": "update_text",
"anchor": "",
"before": "Prices start at 2023 levels.",
"after": "Prices were checked in November 2026."
}
]
}
],
"meta": {
"page": 1,
"per_page": 20,
"total": 1,
"last_page": 1
}
}
One approved page update. Find the page by target.remote_id or target.url (WordPress: url_to_postid(); Shopify: the handle in the URL), compare base_fingerprint if you store one, apply each change, then mark it applied.
import os
import requests
res = requests.get(
"https://mapp.calendone.io/api/v1/websites/7/page-updates/58",
headers={"Authorization": f"Bearer {os.environ['CALENDONE_TOKEN']}"},
)
data = res.json()
package main
import (
"encoding/json"
"net/http"
"os"
)
func main() {
req, _ := http.NewRequest("GET", "https://mapp.calendone.io/api/v1/websites/7/page-updates/58", nil)
req.Header.Set("Authorization", "Bearer "+os.Getenv("CALENDONE_TOKEN"))
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
var data map[string]any
json.NewDecoder(res.Body).Decode(&data)
}
Response · 200
{
"data": {
"id": 58,
"website_id": 7,
"status": "approved",
"operation": "update",
"target": {
"url": "https://fitalert.com/blog/running-shoes-flat-feet",
"remote_id": "post_8812",
"page_type": "post"
},
"keyword": "running shoes for flat feet",
"revision": 2,
"base_fingerprint": "sha256:9b1c…",
"approved_at": "2026-11-19T10:04:12+00:00",
"applied_at": null,
"applied_revision": null,
"changes": [
{
"id": "c1",
"type": "title",
"anchor": "",
"before": "Running shoes for flat feet",
"after": "Best running shoes for flat feet (2026): how to choose"
},
{
"id": "c2",
"type": "meta_description",
"anchor": "",
"before": "",
"after": "What flat feet really need from a running shoe, how to test support in the shop, and five models runners with flat feet like."
},
{
"id": "c3",
"type": "faq",
"anchor": "How to test a shoe",
"before": "",
"after": "## FAQ\n\n### Do flat feet need stability shoes?\nNot always…"
},
{
"id": "c4",
"type": "update_text",
"anchor": "",
"before": "Prices start at 2023 levels.",
"after": "Prices were checked in November 2026."
}
]
}
}
Tell Calendone the approved revision is live on that page. Send the revision you applied; if a newer one was approved meanwhile you get 409 revision_mismatch. Needs write access.
import os
import requests
res = requests.delete(
"https://mapp.calendone.io/api/v1/websites/7/articles/412/publication",
headers={"Authorization": f"Bearer {os.environ['CALENDONE_TOKEN']}"},
)
data = res.json()
package main
import (
"encoding/json"
"net/http"
"os"
)
func main() {
req, _ := http.NewRequest("DELETE", "https://mapp.calendone.io/api/v1/websites/7/articles/412/publication", nil)
req.Header.Set("Authorization", "Bearer "+os.Getenv("CALENDONE_TOKEN"))
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
var data map[string]any
json.NewDecoder(res.Body).Decode(&data)
}
Connect Claude Code, Cursor or any MCP client. Your agent can list approved articles, add them to your codebase or CMS, and report the live URL back. Same token as the REST API.
Try asking your agent: “Check Calendone for approved articles on my site, add them to the blog, and mark them published.”
Webhooks
Let Calendone tell your site when to publish.
Instead of polling, add a URL under Team → API & MCP → Webhooks and choose events. Calendone sends a signed POST with the full article, so your site can publish it straight away.
Events
article.ready_to_publish
An approved article reached its planned publish date and isn’t published yet. Publish now moves its date to today and sends this event immediately.
article.approved
An article was approved in Calendone.
article.ready_for_review
Calendone finished writing an article and it needs approval.
article.updated
A published article was edited in Calendone and your copy is out of date.
page.update_approved
You approved changes to an existing page on your site (from “Improve this page”). Update that page — never create a new one — and reply with the applied revision.
article.ready_to_publish is checked every minute. It fires once per article on its planned date (UTC), or right away if an approved article’s date has already passed. Every event fires once per article; the Send test button sends a ping event.
Request
Header
Value
Calendone-Event
Event name, e.g. article.ready_to_publish.
Calendone-Delivery
Unique delivery id. Retries reuse it, so you can ignore repeats.
Calendone-Timestamp
Unix time when the request was signed.
Calendone-Signature
v1= followed by HMAC-SHA256 of "{timestamp}.{raw body}" using your signing secret, hex encoded.
Body
{
"id": "6f1c2a8e-4b1d-4d1e-9a51-0c7f3b2e9d10",
"event": "article.ready_to_publish",
"created_at": "2026-11-12T00:01:04+00:00",
"team_id": 3,
"website": {
"id": 7,
"url": "https://fitalert.com"
},
"data": {
"article": {
"id": 412,
"website_id": 7,
"status": "approved",
"title": "How to choose running shoes for flat feet",
"slug": "how-to-choose-running-shoes-for-flat-feet",
"excerpt": "What actually matters when you have flat feet, and how to test a shoe before you buy it.",
"language": "en",
"primary_keyword": "running shoes for flat feet",
"planned_for": "2026-11-12",
"revision": 3,
"replaces_article_id": null,
"approved_at": "2026-11-09T08:12:44+00:00",
"created_at": "2026-11-08T21:03:10+00:00",
"updated_at": "2026-11-09T08:12:44+00:00",
"publication": null,
"meta_title": "How to choose running shoes for flat feet",
"meta_description": "What actually matters when you have flat feet, and how to test a shoe before you buy it.",
"featured_image": {
"url": "https://calendone-io.s3.eu-north-1.amazonaws.com/website-content/7/412/cover.webp",
"alt": "Runner tying a stability shoe",
"width": 1536,
"height": 1024
},
"images": [
{
"url": "https://calendone-io.s3.eu-north-1.amazonaws.com/website-content/7/412/cover.webp",
"alt": "Runner tying a stability shoe",
"width": 1536,
"height": 1024
}
],
"content_markdown": "\n\nFlat feet don’t automatically need…\n\n## What support actually means\n…",
"content_html": "<p><img src=\"https://calendone-io.s3.eu-north-1.amazonaws.com/website-content/7/412/cover.webp\" alt=\"Runner tying a stability shoe\" /></p>\n<p>Flat feet don’t automatically need…</p>\n<h2>What support actually means</h2>\n<p>…</p>"
}
}
}
Verify the signature and reply
Check the signature with your signing secret before trusting the request. Answer with any 2xx status. If you publish the article right away, reply with {"url": "…", "remote_id": "…"} and Calendone marks it published, just like the publication endpoint.
$body = $request->getContent();
$timestamp = $request->header('Calendone-Timestamp');
$expected = 'v1='.hash_hmac('sha256', $timestamp.'.'.$body, env('CALENDONE_WEBHOOK_SECRET'));
abort_unless(hash_equals($expected, (string) $request->header('Calendone-Signature')), 401);
abort_if(abs(time() - (int) $timestamp) > 300, 401); // reject old requests
$article = json_decode($body, true)['data']['article'];
// ...save the article, then optionally reply with where it went live:
return response()->json(['url' => "https://fitalert.com/blog/{$article['slug']}"]);
Only HTTPS URLs on the standard port are allowed. Each request times out after 10 seconds, and redirects aren’t followed. If your URL doesn’t answer with 2xx, Calendone retries after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours. After 20 failures in a row the webhook is paused, and you can turn it back on in the app.
Page updates page.update_approved
An opt-in event for changes to an existing page that the owner approved in Calendone (“Improve this page”). Update the page in target: find it by target.remote_id or target.url (WordPress: url_to_postid(); Shopify: the handle in the URL). Never create a new page. If the page is missing or changed since base_fingerprint, answer 404 or 409: Calendone stops retrying and shows the owner the error. When done, reply {"url": "…", "remote_id": "…", "applied_revision": 2}. Ignore a revision you already applied. The same updates are in GET /websites/{website_id}/page-updates.
Change type
How to apply it
title
Replace the page’s SEO title (<title>). before = current value.
meta_description
Replace the meta description.
h1
Replace the main heading.
update_text
Replace the exact passage in before with after. If before isn’t on the page any more, skip the change and report a conflict.
add_section
Insert after (Markdown) right after the heading named in anchor, or at the end of the main content when anchor is "end".
faq
Same as add_section: a Markdown FAQ block.
internal_link
Same as add_section: a sentence with a link to another page on your site.
alt_text
Set the alt text of the image whose src is in anchor.
Body
{
"id": "0d6b51f2-6f0a-4f5e-8f2e-7f1f8a3c2b41",
"event": "page.update_approved",
"created_at": "2026-11-19T10:05:01+00:00",
"team_id": 3,
"website": {
"id": 7,
"url": "https://fitalert.com"
},
"data": {
"page_update": {
"id": 58,
"website_id": 7,
"status": "approved",
"operation": "update",
"target": {
"url": "https://fitalert.com/blog/running-shoes-flat-feet",
"remote_id": "post_8812",
"page_type": "post"
},
"keyword": "running shoes for flat feet",
"revision": 2,
"base_fingerprint": "sha256:9b1c…",
"approved_at": "2026-11-19T10:04:12+00:00",
"applied_at": null,
"applied_revision": null,
"changes": [
{
"id": "c1",
"type": "title",
"anchor": "",
"before": "Running shoes for flat feet",
"after": "Best running shoes for flat feet (2026): how to choose"
},
{
"id": "c2",
"type": "meta_description",
"anchor": "",
"before": "",
"after": "What flat feet really need from a running shoe, how to test support in the shop, and five models runners with flat feet like."
},
{
"id": "c3",
"type": "faq",
"anchor": "How to test a shoe",
"before": "",
"after": "## FAQ\n\n### Do flat feet need stability shoes?\nNot always…"
},
{
"id": "c4",
"type": "update_text",
"anchor": "",
"before": "Prices start at 2023 levels.",
"after": "Prices were checked in November 2026."
}
]
}
}
}
// After verifying the signature (see above):
$update = json_decode($body, true)['data']['page_update'];
$postId = (int) ($update['target']['remote_id'] ?? 0) ?: url_to_postid($update['target']['url']);
if (! $postId) {
return new WP_REST_Response(['error' => 'page_not_found'], 404); // never create a new post
}
if (get_post_meta($postId, '_calendone_revision', true) >= $update['revision']) {
return ['url' => get_permalink($postId), 'remote_id' => (string) $postId, 'applied_revision' => $update['revision']]; // already applied
}
foreach ($update['changes'] as $change) {
// title → post title / SEO plugin title, meta_description → SEO plugin field,
// update_text → replace $change['before'] with $change['after'] in post_content,
// add_section / faq / internal_link → insert converted Markdown after the heading in $change['anchor'] ("end" = append)
}
update_post_meta($postId, '_calendone_revision', $update['revision']);
return ['url' => get_permalink($postId), 'remote_id' => (string) $postId, 'applied_revision' => $update['revision']];
const { page_update: update } = JSON.parse(req.body).data;
const page = await db.pages.findOne(update.target.remote_id ? { id: update.target.remote_id } : { url: update.target.url });
if (!page) return res.status(404).json({ error: 'page_not_found' }); // never create a new page
if (page.calendoneRevision >= update.revision) {
return res.json({ url: page.url, remote_id: page.id, applied_revision: update.revision }); // already applied
}
if (page.calendoneFingerprint && page.calendoneFingerprint !== update.base_fingerprint) {
// optional: your page changed since Calendone read it — apply carefully or answer 409
}
for (const change of update.changes) applyChange(page, change); // see the change types table
page.calendoneRevision = update.revision;
await db.pages.save(page);
res.json({ url: page.url, remote_id: page.id, applied_revision: update.revision });
Errors
Errors return {"error": {"code": "...", "message": "..."}} with a matching HTTP status.
Status
Code
Meaning
401
—
Missing, wrong or revoked token. Body: {"message": "Unauthenticated."}
403
forbidden
The token is read-only and the endpoint needs write access.