Display Klusio blogs on your own website
The API is a secure connection that lets your website retrieve published blogs from Klusio. It returns data in JSON. Your website then determines how the title, image and text are displayed.
What exactly happens?
Your web developer needs your company ID, API key and this page. Share the key through a secure password manager, never in a public email or document.
Quick start
- While logged in, create an API key under Settings → API.
- Copy the key immediately; Klusio displays it in full only once.
- Have your website send the key from the server .
- Retrieve one article first, then check its appearance.
Base URL
https://klusio.nl/api/v1/blogsFirst test with cURL
curl --request GET \
--url "https://klusio.nl/api/v1/blogs?company_id=YOUR_COMPANY_ID&limit=1" \
--header "X-API-Key: YOUR_API_KEY"A successful request returns HTTP status 200 and starts with {"success":true.
Use your API key securely
An API key works like a password for the integration. Preferably send it in the header X-API-Key. A Bearer header is also supported.
X-API-Key: YOUR_API_KEY
# Alternative
Authorization: Bearer YOUR_API_KEYEvery visitor can inspect JavaScript and network requests. Use PHP, Node.js, Python, a serverless function or your CMS's secure storage. Do not put the key in a URL as ?api_key=... ; API v1 deliberately rejects this.
- Give each website or integration its own key with a recognisable name.
- Disable a key when an integration is temporarily stopped.
- Delete and replace any key that may have leaked.
- Set an expiry date for temporary external access.
What data can you retrieve?
Use one main selection per request: a list, one article, a topic, a pillar or related articles. Do not combine slug, topic_id, pillar_url and related_to ; the API rejects an ambiguous request with HTTP 400.
| Goal | Example after the base URL | What you get |
|---|---|---|
| Latest articles | ?company_id=YOUR_COMPANY_ID&limit=10 | A list with a total and an offset. |
| One complete article | ?company_id=YOUR_COMPANY_ID&slug=mijn-artikel | Full content, SEO data and tracking. |
| One topic | ?company_id=YOUR_COMPANY_ID&topic_id=5 | Articles and pillar information for the topic. |
| Topic for a pillar | ?company_id=YOUR_COMPANY_ID&pillar_url=https%3A%2F%2Fvoorbeeld.nl%2Fdienst | The topic associated with that full URL. |
| Related articles | ?company_id=YOUR_COMPANY_ID&related_to=mijn-artikel&limit=3 | Up to three relevant articles. |
List parameters
| Parameter | Required? | Meaning |
|---|---|---|
company_id | YES | The Klusio company number. |
limit | No | Number of articles; 20 by default, with a maximum of 100. |
offset | No | Number of articles to skip, useful for pagination. |
search | No | Searches the title, meta description and article text; up to 200 characters. |
sort | No | recent, oldest, popular or reading-time. |
author_id | No | Shows only articles by one Klusio author. |
include | No | topics,authors also returns topics with their pillar pages and the authors, so you can place articles on the appropriate service and author pages. |
Each article in a list also has url (the full address in your site’s URL format), updated_at, topic_id, author_id and noindex.
Lists contain only published, visible articles that meet the company's blog settings. A direct slug request can always retrieve a visible, published article.
What a response looks like
Article list
{
"success": true,
"total": 75,
"limit": 1,
"offset": 0,
"posts": [{
"id": 2042,
"slug": "voorbeeld-artikel",
"title": "Voorbeeldtitel",
"meta_description": "Korte omschrijving voor Google.",
"featured_image": "https://voorbeeld.nl/afbeelding.webp",
"featured_image_alt": "Beschrijving van de afbeelding",
"author": "Naam auteur",
"published_at": "2026-08-12 09:00:00",
"reading_time": 6,
"views_count": 123,
"is_indexed": true,
"content_type": "how_to_guide"
}],
"reviews": {
"google_rating": 4.8,
"total_reviews": 47,
"rating_distribution": {"5":42,"4":3,"3":1,"2":0,"1":1},
"business_name": "Voorbeeldbedrijf",
"latest_reviews": []
},
"filters_applied": {
"search": null,
"sort": "recent",
"visibility": {"min_views":0,"require_indexed":false,"hide_after_days":null}
}
}The list deliberately excludes the full article text. Retrieve an individual article using slug.
One complete article
The single-post response contains post , including content, meta_description, featured_image, cta_text, cta_link, topic fields and any FAQ, HowTo and claim data. You also receive:
author_detailsandreviewer_detailsfor visible expertise blocks;schema_markupandseo_headfor correct SEO output;pillar_postwhen the article is linked to a main page;tracking_scriptandtracking_tokenfor secure page-view measurement;reviewswith the most recently synchronised Google reviews.
post.content, seo_head, schema_markup and tracking_script contain HTML. Insert this directly only if the response genuinely comes from Klusio and the API request succeeded.
Complete PHP example
This example retrieves five blogs on the server. The API key is stored in an environment variable, so it never reaches the browser.
<?php
$apiKey = getenv('KLUSIO_API_KEY');
$url = 'https://klusio.nl/api/v1/blogs?company_id=YOUR_COMPANY_ID&limit=5&sort=recent';
$ch = curl_init($url);
curl_setopt_array($ch, [
CURLOPT_RETURNTRANSFER => true,
CURLOPT_TIMEOUT => 15,
CURLOPT_HTTPHEADER => [
'Accept: application/json',
'X-API-Key: ' . $apiKey,
],
]);
$body = curl_exec($ch);
$status = curl_getinfo($ch, CURLINFO_HTTP_CODE);
$curlError = curl_error($ch);
curl_close($ch);
if ($body === false || $curlError !== '') {
throw new RuntimeException('Klusio API is unreachable: ' . $curlError);
}
$data = json_decode($body, true, 512, JSON_THROW_ON_ERROR);
if ($status !== 200 || empty($data['success'])) {
throw new RuntimeException($data['error'] ?? 'Unknown API error');
}
foreach ($data['posts'] as $post) {
echo '<a href="/blog/' . rawurlencode($post['slug']) . '">';
echo htmlspecialchars($post['title'], ENT_QUOTES, 'UTF-8');
echo '</a>';
}Measure article views
When you retrieve one article using slug , Klusio provides a ready-to-use tracking_script. That script uses a short-lived token specific to the article and company.
// After a successful single-post request:
echo $data['post']['content'];
echo $data['tracking_script']; // preferably just before </body>For your own implementation, send a POST to https://klusio.nl/api/v1/track with post_id, company_id and the returned tracking_token. Optional fields are visitor_id, time_spent, scroll_depth, referrer and converted.
Static pages or your own cache
If your site builds articles into pages on the server, retrieve an article with count_view=0: that server request is not a reader. Send the reader’s measurement from your own server using the same POST, but put the API key in X-API-Key instead of tracking_token. Klusio then stores neither your server’s IP address nor its browser. Never put the API key in the browser.
If your site has a synchronisation endpoint (for example /klusio/sync.php), Klusio calls it just before checking whether a new or updated article is live. Ask Klusio to configure that endpoint.
Articles in other languages
When the company switches on a language under Blog › Settings in Klusio, Klusio translates every new approved article and adds it to the API with lang. This is available from Groei Pro. The content is the same as in Dutch; Klusio checks the translation for meaning, numbers, names and links.
| Goal | Example after the base URL | What you get |
|---|---|---|
| English articles | ?company_id=YOUR_COMPANY_ID&lang=en&limit=10 | The translated articles, newest first. sort, topic_id, author_id and related_to work as well. |
| One English article | ?company_id=YOUR_COMPANY_ID&lang=en&slug=engelse-slug | The same as a Dutch article, with translated title, text, meta description and button text. The slug of the Dutch original also works. |
Every article has language and translations: per translation the language, slug, title, url and live. A single article also has alternates (hreflang to address), and seo_head contains the same lines.
"language": "nl",
"translations": [
{
"language": "en",
"slug": "how-to-choose-a-roofer",
"title": "How to choose a roofer",
"url": "https://voorbeeld.nl/en/blog/how-to-choose-a-roofer/",
"live": false
}
]How to show them on your website
Show the translation at the address in url . The company chooses that address under Blog › Settings; by default it is /en/blog/<slug>/. Build a language switch on the page with translations.
After publication, Klusio checks whether the translation is at that address. Only then does live become true and are the hreflang lines added to seo_head of the Dutch article and to the sitemap. Google is never pointed to a page your site does not show yet.
Measure identifiable AI traffic
Report click-throughs from AI assistants and visits from AI crawlers from your own server using POST /api/v1/ai-traffic. Klusio does not have a WordPress plugin for this. Send the API key through X-API-Key. Klusio accepts only recognisable AI referrals and AI user agents; a regular Googlebot, Bingbot or search-engine referral does not count as AI.
{
"event_type": "crawler",
"event_key": "unieke-idempotency-key-per-request",
"landing_url": "https://voorbeeld.nl/dienstpagina",
"user_agent": "OAI-SearchBot/1.0"
}Klusio does not store IP addresses, full user agents or query strings. A crawler hit means a request carried a known AI crawler identity; only an explicit browser referral counts as a measured click-through from an AI assistant.
Google reviews
Responses contain the most recently synchronised review summary: average rating, review count, breakdown by star rating, business name and up to ten visible recent reviews. This data is not updated live every second; Klusio refreshes it periodically, normally daily.
When Google reviews are not connected or have not yet been retrieved, reviews may be empty or contain zero values. Build your website so that the review block remains neatly hidden in that case.
Understand errors
Every error contains success: false, a readable error, a fixed error_code and a request_id. Give that request ID to support; technical server details remain safely in the log.
{
"success": false,
"error": "Een geldige API-key is verplicht. Gebruik de X-API-Key-header.",
"error_code": "invalid_api_key",
"request_id": "a1b2c3d4e5f60708"
}| Status | Meaning | What to do |
|---|---|---|
400 | Invalid request | Check the company ID, URL and parameters. |
401 | API key or tracking token is missing or invalid | Check the header or retrieve a new tracking token. |
403 | Key is disabled, expired, lacks read access or belongs to another company | Check the key in API management. |
404 | Article or topic does not exist | Check the slug or topic. If an article has moved, redirect_to is included in the response. |
405 | Incorrect HTTP method | Use GET for blogs and POST for tracking. |
429 | Hourly limit reached | Wait as specified by Retry-After and use caching. |
500 | Internal error | Save request_id and contact support. |
Limits and caching
New keys default to 100 requests per hour. In API management, you can set a per-key limit from 1 to 1,000. After valid authentication, usage appears in these response headers:
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 96
X-RateLimit-Reset: 1786525200- Cache an article list for 5 to 15 minutes.
- Cache a full article for up to one hour.
- Do not refresh Google reviews more than once a day.
- For HTTP 429, use the
Retry-Afterheader; do not keep retrying immediately.
Existing integrations
The old endpoint /api/blog.php remains available for now so existing websites do not break unexpectedly. New integrations must always use /api/v1/blogs . V1 has mandatory authentication, consistent validation and predictable error codes.
First change the endpoint and send the key through X-API-Key. Test lists, single posts, redirects and tracking. Only then switch off the old integration.
Need help?
Send the following to support@klusio.nl: your company_id, the endpoint used, the HTTP status, the request_id and the time. Never send anyone your full API key.


