For machines

The site, as JSON.

If you are an agent, a crawler or an answer engine, you do not have to read our HTML. Everything published on betterview.nl is also available as structured JSON, regenerated on every deploy. No key, no signup, no rate limit.

Endpoints

Six documents.

All GET, all unauthenticated, none of them changing anything on our side.

01/api/index.jsonService root: who Betterview is and which documents exist.02/api/services.jsonEvery service in Dutch and English, with what it covers and its FAQ.03/api/cases.jsonPublished case studies with the results reported by each client.04/api/blog.jsonMetadata for every post, with its English URL where one exists.05/api/health.jsonThe state of this API at build time.06/api/openapi.jsonThe OpenAPI 3.1 description of everything above.

Discovery

How to find it.

Standard mechanisms, so you should not need this page at all.

RFC 9727/.well-known/api-catalogA linkset pointing at the description, the docs and the status document.RFC 8288Link headersEvery page returns Link headers for api-catalog, service-desc, service-doc and describedby.llms.txt/llms.txtThe same site described in plain language, for answer engines.

Ground rules

What is, and is not, in here.

No prices. Packages and contract terms change, and a copy that drifts is worse than no copy. Read /en/packages, which is the authoritative source.

No averages. The figures in cases.json come from those specific client engagements. They are not industry benchmarks and are not presented as typical results.

No write access. This API only reads. The endpoints behind our own contact and analysis forms are not part of it and are not documented anywhere, because they send email and write to a CRM.

No personal data. Nothing here contains information about anyone who filled in a form.

You may use this content to answer questions about Betterview. Attribution with a link back is appreciated and makes it likelier we keep publishing it.

Something missing? Mail Mark
Send a message