REST API Overview & Auth
Integrate ZyVOP publishing directly into your headless CMS, CI pipelines, and developer workflows.
REST API Overview & Authentication
ZyVOP exposes a developer-first REST API enabling you to publish and syndicate articles programmatically from static site builders, headless CMS webhooks (Sanity, Strapi, Contentful), or automated Git pipelines.
Base URL
All requests must be made over HTTPS to:
https://zyvop.com/api/v1Authentication
Authentication is performed using Developer Tokens. Every developer token begins with the prefix zv_ followed by 48 hexadecimal characters.
Authorization: Bearer zv_<48-hex-character-token>Generating Developer Tokens
You can generate and revoke developer tokens at any time in your ZyVOP Developer Settings. Tokens authorize the documented developer REST API and MCP tools for your account; they are not web-session or GraphQL credentials.
Example cURL Request
curl -X POST https://zyvop.com/api/v1/articles \
-H "Authorization: Bearer $ZYVOP_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"content": "---\ntitle: \"Distributed Tracing\"\ncanonical_url: \"https://myblog.dev/tracing\"\n---\n\n# Distributed Tracing\n\nDeep dive into OpenTelemetry..."
}'Idempotent Upserts
The ZyVOP API is natively idempotent. When you send an article payload, ZyVOP determines whether to create a new post or update an existing one authored by you by matching:
- Frontmatter
idor bodyid - Frontmatter
slugor bodyslug - Frontmatter
canonical_url - Post
title
If a matching post exists in your account, it updates the content and returns "action": "updated". Otherwise, it creates a new post and returns "action": "created". This makes CI/CD workflows safe against duplicate posts on rerun.
Endpoints
| Method | Endpoint | Description |
|---|---|---|
POST | /api/v1/articles | Publish or update a Markdown article with cross-posting |