NexoFlow Developer API
Use NexoFlow as a headless CMS backend: the supported path is the official nexoflow-sdk on npm, which wraps the same REST endpoints documented here. Create a key under Project → Settings → Developer API. Full SDK reference (methods, frameworks, errors) lives in nexoflow-sdk docs.
Authentication
JWT-based API access: send your project secret as a Bearer token. The SDK sets this for you from apiKey.
HTTP Bearer
Authorization: Bearer <your-api-key>
Missing or invalid keys receive 401. Keep keys on the server-never expose them in the browser bundle.
Base URL
Production v1 API:
https://nexoflow.net/api/v1Content endpoints
These routes back the content methods on nexoflow-sdk. Use plain HTTP if you are not on Node-or wrap them in your own client.
Authenticated requests- GET
/content/postsList published posts
Paginated list. Query: page, limit, tag, category, sort (newest | oldest).
- GET
/content/posts/{slug}Get post by slug
Single post with body, metadata, and SEO fields.
- GET
/content/posts/slugsList all post slugs
For static generation (e.g. Next.js generateStaticParams).
Response shapes
Exact field names and TypeScript types ship with nexoflow-sdk. At a glance:
Post list items
What you get from posts.list - ids, slugs, titles, and fields needed for indexes and cards (see nexoflow-sdk types).
Pagination
page, limit, total, hasMore - returned alongside list endpoints.
Single post
Full post payload for fetch-by-slug, including body and SEO-related fields.
Next steps
Deeper walkthroughs, webhooks, and product context live outside this reference page.
Keys & security
Treat API keys like passwords-scope per project and rotate if they leak.
Security & trust