All integrations
Live
One JSON endpoint for any custom stack
Next.js, Astro, Nuxt, Laravel or anything else: fetch your published posts server side from a single authenticated endpoint and render them in your own templates.
Setup in three steps
- 1Create an API key per site
- 2Fetch /v1/posts server side
- 3Render with your own components
What you get
- Clean HTML and markdown in one payload
- Webhook ping on publish
- Full export any time
Workflow
Approve once, then it lands in Content API
Choose auto publish and articles go live on the schedule you set. Choose review first and nothing moves until a team member signs off.
Draft→
Review→
Published
Week 14
3/weekMon
Best coffee cart software for accounting
BlogTue
Coffee Cart Texas
PageWed
Coffee cart pricing explained
BlogThu
no post
Fri
Coffee cart Texas: full guide
BlogHire Coffee Cart Wedding
PageSat
no post
How the connection works
What Rankdesk does inside Content API
Pull based. You call the Rankdesk Content API from your own stack and render the JSON yourself.
What you need first
- A server side environment that can hold an API key
- Routes for the list and the detail page
Good to know
- You own the rendering, so SEO tags and the sitemap are your responsibility.
- Rate limits apply per key, which is plenty for normal blog traffic with caching.
Field mapping to Content API
| Rankdesk | Content API |
|---|---|
| GET /v1/posts | Paginated list with title, slug, excerpt, image |
| GET /v1/posts/:slug | Full article as HTML and as markdown |
FAQ
