Skip to main content
Skip to content
Browse the docs

Developer Guide

Overview

Show your Lernmark programmes on your school's own website. A small public API returns your live programme catalogue: titles, awards, durations, summaries, and whether applications are open. Your web developer fetches it on your server and presents it in your own design. For most sites this is an afternoon of work.

At a glanceDetails
API base URLhttps://api.lernmark.app
AuthenticationNone. No API key, token, or cookie.
AccessRead-only. Returns only what your school has approved for public listing.
FormatJSON over HTTPS
PlanPlatform plan, with Admissions

Choose your path

Path A

Lernmark hosts your site

For schools with no website, or happy to replace the one they have. You get a ready-made, accessible public site that stays in step with your programmes. Your team edits the content; there is no code to maintain. Contact us to discuss it.

Path B

Add programmes to your own site

For schools with a website to keep. A developer adds a small server-side integration and shows the programmes in your existing design, on your own domain. Your school owns that code.

As a rule of thumb: no website or no developer, choose Path A. An established website and a developer, choose Path B. The rest of this guide covers Path B.

Three rules for a reliable integration

  1. Call the API from your server. Fetch the programmes in your server-side code and send finished HTML to the browser. Visitors and search engines then see the programmes in the page itself, and you control caching and errors in one place.
  2. Cache successful responses for 5–15 minutes. Pages stay fast, a short Lernmark outage goes unnoticed, and your site stays well inside the rate limits.
  3. Fail closed. On any error or timeout, show “Programme information is temporarily unavailable.” Never show guessed, placeholder, or expired programme details.

What you will build

If something does not work, start with Troubleshooting & FAQ.