API
Content API
The Content API is a simple read-only pull endpoint per project for approved or published content.
- Updated
- 2026-04-19
- Availability
- Płatne plany, token dla projektu
Overview
The API returns the same underlying content that can move to publish in the WordPress flow. Custom stacks fetch it with a bearer token and deploy it in their own process.
text
Base URL
https://app.nelavio.comEndpoints
GET
/api/v1/projects/:projectId/contentReturns a paginated list of content items available to the project token.
Headers
Authorization: Bearer <token>
Query
- state=approved|published, default approved
- operation=create|update|all, default all
- page=number, default 1
- per_page=number, default 20, max 50
Responses
- 200 data + meta
- 400 INVALID_QUERY_PARAMS
- 401/403 auth or entitlement
- 429 RATE_LIMITED
bash
curl -H "Authorization: Bearer nla_example" \
"https://app.nelavio.com/api/v1/projects/proj_123/content?state=approved&per_page=20"GET
/api/v1/projects/:projectId/content/:contentItemIdReturns a single content item as JSON or Markdown.
Headers
Authorization: Bearer <token>If-None-Match: "<etag>" optional
Query
- version=latest|number, default latest
- format=json|markdown, default json
Responses
- 200 content item
- 304 not modified
- 404 CONTENT_NOT_FOUND
- 429 RATE_LIMITED
bash
curl -H "Authorization: Bearer nla_example" \
"https://app.nelavio.com/api/v1/projects/proj_123/content/item_456?format=markdown"Configure a token
The API token is generated per project and should be stored as a secret.
