Complete API documentation for Wrodium's CMS integration endpoints.
Created date:
Dec 5, 2025
Updated date:
Dec 11, 2025
Base URL
Authentication
All API requests require authentication via Bearer token:
Get your API key from Settings → API in your Wrodium dashboard.
Endpoints
List CMS Articles
Retrieve articles from your connected CMS.
Path Parameters
Parameter | Type | Required | Description |
|---|---|---|---|
| string | Yes | Your brand identifier |
Query Parameters
Parameter | Type | Default | Description |
|---|---|---|---|
| integer | 20 | Number of articles (1-100) |
Response
Response Fields
Field | Type | Description |
|---|---|---|
| string | Unique article identifier from CMS |
| string | CMS provider ( |
| string | Article title (HTML stripped) |
| string | Article excerpt or summary |
| string | ISO 8601 publication date |
| integer | Approximate word count |
| string |
|
| string | Public URL (if available) |
| object | Original CMS payload (for debugging) |
Example Request
Errors
Code | Description |
|---|---|
401 | Invalid or missing API key |
404 | Brand not found or CMS not configured |
502 | CMS connection failed |
Update CMS Article
Push optimized content back to your CMS.
Request Body
Request Fields
Field | Type | Required | Description |
|---|---|---|---|
| string | Yes | Your brand identifier |
| string | Yes | CMS article ID to update |
| string | No | New title |
| string | Yes | Updated HTML content |
| string | No | New excerpt |
| string | No | New URL slug |
| boolean | No | Whether to publish (default: true) |
Response
Returns the updated ArticleSummary object:
Example Request
Errors
Code | Description |
|---|---|
401 | Invalid or missing API key |
404 | Brand or article not found |
422 | Invalid content or validation error |
501 | CMS doesn't support updates (e.g., Framer) |
502 | CMS update failed |
Get CMS Configuration
Retrieve your CMS connection settings (without sensitive credentials).
Response
Test CMS Connection
Verify your CMS connection is working.
Response
Data Models
ArticleSummary
Normalized article representation across all CMS providers.
ArticleUpdateInput
Input for updating an article.
UpdateArticleRequest
Full request body for the update endpoint.
CMS Provider Specifics
WordPress
Uses REST API v2
Authentication: Application Passwords
Content field:
content.rendered→contentSupports custom post types via configuration
Webflow
Uses Data API v2
Requires field ID mapping in configuration
Updates go to
/items/{id}/liveendpointSupports localization
Contentful
Uses Content Management API (CMA)
Requires optimistic locking (
X-Contentful-Version)All fields are locale-specific
Updates create new versions (not auto-published)
Ghost
Uses Admin API with JWT authentication
Requires
updated_atfor collision detectionSupports HTML and Lexical content formats
Custom Webhook
You define pull and update endpoints
Must return normalized article format
Supports custom authentication headers
Rate Limits
Endpoint | Rate Limit |
|---|---|
GET /cms/articles | 60 requests/minute |
POST /cms/update-article | 30 requests/minute |
GET /cms/config | 60 requests/minute |
POST /cms/test-connection | 10 requests/minute |
Rate limit headers are included in responses:
Error Responses
All errors follow this format:
Common Error Codes
Code | HTTP Status | Description |
|---|---|---|
| 401 | Missing or invalid API key |
| 404 | Resource not found |
| 422 | Invalid request data |
| 404 | CMS not connected |
| 502 | Could not reach CMS |
| 502 | CMS rejected update |
| 501 | Operation not supported |
| 429 | Too many requests |
SDKs
Python
JavaScript/TypeScript
Webhooks
Wrodium can send webhooks when CMS operations complete.
Events
Event | Description |
|---|---|
| Article successfully updated |
| Article update failed |
| Full sync completed |
Payload
Configure webhooks in Settings → Webhooks.



