Content API
Let a custom website securely read published Surpasso articles.
Choose Content API when a custom website already has its own pages, content store, or rendering system. The website asks Surpasso for published articles; Surpasso does not push content into the site.
Before you start
You need a developer who can update the website's server-side code and deployment environment. The API key must never be placed in browser code.
Create the connection
- Open Workspace → Integrations and choose Content API.
- Give the connection a recognizable name.
- Select Create API key.
- Copy the key immediately. The full value is shown only once.
- Store it in a server-side environment variable.
Read articles
GET /api/content/v1/articles
GET /api/content/v1/articles?limit=50
GET /api/content/v1/articles?updated_since=2026-10-13T00:00:00.000Z
GET /api/content/v1/articles/<article-id-or-slug>
Authorization: Bearer sp_content_...The API returns published articles only. Surpasso drafts stay private. The
maximum page size is 50; updated_since is useful when an existing content
store only needs changed articles.
Successful responses include ETag and, when content is present,
Last-Modified. Send If-None-Match or If-Modified-Since on later requests;
an unchanged result returns 304 without a response body. Each key can make up
to 120 requests per minute. A 429 response includes Retry-After.
Security and updates
- Keep the key in server environment variables and out of client bundles.
- Cache responses according to the website's publishing needs.
- Use conditional requests instead of downloading unchanged article bodies.
- Rotate the key immediately if it appears in a Git commit, browser bundle, or screenshot.
- Use the Next.js guide instead if the site uses Next.js and would benefit from a ready-made blog starter.