Site API#

Read and write the content of one NAMES LEGAL site over HTTPS: services, projects, blog posts, team members, events, jobs, FAQ and more. The API is part of the API access add-on of the site.

Quick start#

1. In the console of the site, Add-ons & subscription: activate API access.
2. Modules → API: create a key. Copy it now — it is shown only once.
3. Call the API:

KEY="nlk_3fa9c2d1_Jx0..."
curl -H "Authorization: Api-Key $KEY" "https://ecolehorizon.names.legal/api/v1/team/?lang=fr"

{
  "count": 12,
  "next": "https://ecolehorizon.names.legal/api/v1/team/?lang=fr&page=2",
  "previous": null,
  "results": [
    {"id": 4, "first_name": "Awa", "last_name": "Diop", "position": "Mathematics teacher",
     "profile_image": "https://ecolehorizon.names.legal/media/demo/team/awa.jpg",
     "updated_at": "2026-09-20T08:12:44+02:00"}
  ]
}

Base URL#

https://<site>/api/v1/

<site> is the site's own address (ecolehorizon.names.legal or its custom domain). There is no language prefix in the path. v1 is the only version; a breaking change would come as v2 alongside it.

The root URL lists every collection. An interactive reference (Swagger) and the OpenAPI schema are available on each site:

Authentication#

1. The site owner activates the API access add-on.
2. In the console, Modules → API, they create a key and choose its scope. The full key is shown once; only a prefix and a hash are stored.
3. Send the key with every request.

GET /api/v1/services/ HTTP/1.1
Host: ecolehorizon.names.legal
Authorization: Api-Key nlk_3fa9c2d1_Jx0...

Authorization: Bearer <key> and X-Api-Key: <key> are accepted as well. Keys look like nlk_<8 hex characters>_<secret>.

Scopes#

The scope applies to the whole key; there is no per-collection scope. A key can be revoked at any time from the console.

Errors you may meet#

Language#

Translated fields are returned in one language at a time. Choose it with ?lang=:

curl -H "Authorization: Api-Key $KEY" "https://ecolehorizon.names.legal/api/v1/services/?lang=fr"

The language must be one of the languages published by the site; otherwise the answer is 400. Without lang, the site's default language is used. The response carries a Content-Language header.

Pagination, filters and sorting#

Lists are paginated by page number:

{
  "count": 42,
  "next": "https://ecolehorizon.names.legal/api/v1/team/?page=2",
  "previous": null,
  "results": [ ... ]
}

since makes incremental synchronisation cheap: store the time of your last call and pass it next time.

Rate limits#

• 120 requests per minute per API key (each key has its own counter).
• Console sessions: 120 per minute. Anonymous calls: 30 per minute.

Past the limit the API answers 429; wait and retry.

Collections#

Each entry is reachable at <collection>/<id>/. The fields of every collection are listed in the reference below.

Writing#

• POST creates, PUT replaces, PATCH updates some fields.
• Categories are read as an object {"id", "name", "slug"} and written with category_slug. An unknown slug is refused.
• Images and files are read-only in the API: upload them in the console, or let the data connector download them from a URL.
• HTML sent in rich-text fields is cleaned: scripts and event handlers are removed.

curl -X POST "https://ecolehorizon.names.legal/api/v1/faq/?lang=fr" \
  -H "Authorization: Api-Key $KEY" -H "Content-Type: application/json" \
  -d '{"question": "Quand ont lieu les inscriptions ?", "answer": "<p>Du 1er au 30 juin.</p>"}'

Booking an appointment#

curl -X POST "https://ecolehorizon.names.legal/api/v1/bookings/" \
  -H "Authorization: Api-Key $KEY" -H "Content-Type: application/json" \
  -d '{"item": 3, "customer_name": "Awa Diop", "customer_email": "awa@example.com",
       "date": "2026-10-02", "time": "14:30"}'

time is in the site's time zone. A slot that is no longer free is refused with 400. New bookings start as pending.

Recipes#

Mirror a collection incrementally#

Read everything once, then only what changed. Keep the time of your previous run and pass it as since.

Python

import time
import requests

BASE = "https://ecolehorizon.names.legal/api/v1/"
HEADERS = {"Authorization": "Api-Key nlk_3fa9c2d1_Jx0..."}

def fetch_all(collection, since=None, lang="fr"):
    url = f"{BASE}{collection}/"
    params = {"lang": lang, "page_size": 100, "ordering": "updated_at"}
    if since:
        params["since"] = since
    while url:
        response = requests.get(url, headers=HEADERS, params=params, timeout=15)
        if response.status_code == 429:
            time.sleep(int(response.headers.get("Retry-After", "5")))
            continue
        response.raise_for_status()
        data = response.json()
        yield from data["results"]
        url, params = data["next"], None   # "next" already carries the parameters

for member in fetch_all("team", since="2026-09-01T00:00:00Z"):
    print(member["id"], member["first_name"], member["last_name"])

JavaScript (Node.js 18+)

const BASE = "https://ecolehorizon.names.legal/api/v1/";
const HEADERS = { Authorization: "Api-Key nlk_3fa9c2d1_Jx0..." };

async function* fetchAll(collection, since, lang = "fr") {
  const first = new URL(`${BASE}${collection}/`);
  first.search = new URLSearchParams({ lang, page_size: "100", ordering: "updated_at",
                                       ...(since ? { since } : {}) });
  let url = first.toString();
  while (url) {
    const response = await fetch(url, { headers: HEADERS });
    if (response.status === 429) {
      const wait = Number(response.headers.get("Retry-After") || 5);
      await new Promise((resolve) => setTimeout(resolve, wait * 1000));
      continue;
    }
    if (!response.ok) throw new Error(`${response.status} ${await response.text()}`);
    const data = await response.json();
    yield* data.results;
    url = data.next;
  }
}

for await (const post of fetchAll("blog", "2026-09-01T00:00:00Z")) {
  console.log(post.id, post.title);
}

Create or update an entry#

PHP

<?php
$base = 'https://ecolehorizon.names.legal/api/v1/';
$headers = ['Authorization: Api-Key nlk_3fa9c2d1_Jx0...', 'Content-Type: application/json'];

function call($method, $url, $headers, $body = null) {
    $ch = curl_init($url);
    curl_setopt_array($ch, [CURLOPT_CUSTOMREQUEST => $method, CURLOPT_HTTPHEADER => $headers,
                            CURLOPT_RETURNTRANSFER => true, CURLOPT_TIMEOUT => 15]);
    if ($body !== null) curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode($body));
    $answer = curl_exec($ch);
    $status = curl_getinfo($ch, CURLINFO_RESPONSE_CODE);
    curl_close($ch);
    return [$status, json_decode($answer, true)];
}

// Create an event (in French)
[$status, $event] = call('POST', $base . 'events/?lang=fr', $headers, [
    'title' => 'Journée portes ouvertes',
    'slug' => 'journee-portes-ouvertes-2026',
    'description' => '<p>Visite du campus et rencontre avec les enseignants.</p>',
    'start_date' => '2026-11-14T09:00:00+01:00',
    'end_date' => '2026-11-14T16:00:00+01:00',
    'location' => 'Campus de Genève',
]);

// Change only the location later
call('PATCH', $base . "events/{$event['id']}/?lang=fr", $headers, ['location' => 'Aula']);

lang decides which language a translated field is written to: send the same entry again with ?lang=en to add the English version.

Errors and limits in practice#

Reference by collection#

Generated from the code of the API: fields, access rights and query parameters are always those of the running platform. Translated fields are read and written in the language chosen with lang.

/api/v1/services/

GETPOSTPUTPATCH

• Filters slug category__slug is_featured
• search title description
• ordering order title updated_at (default order)

/api/v1/projects/

GETPOSTPUTPATCH

• Filters slug category__slug status is_featured
• search title description client technologies
• ordering order title project_date updated_at (default order)

/api/v1/blog/

GETPOSTPUTPATCH

• Filters slug category__slug status tags__slug
• search title excerpt content
• ordering published_date title updated_at (default -published_date)

/api/v1/team/

GETPOSTPUTPATCH

• Filters member_type is_featured
• search first_name last_name position specialties
• ordering order last_name updated_at (default order)

/api/v1/testimonials/

GETPOSTPUTPATCH

• Filters rating
• search name position testimonial
• ordering order rating updated_at (default order)

/api/v1/publications/

GETPOSTPUTPATCH

• Filters slug category__slug year is_featured
• search title authors journal abstract
• ordering order year title updated_at (default order,-year)

/api/v1/resources/

GETPOSTPUTPATCH

• Filters slug resource_type is_free
• search title description
• ordering order title created_at updated_at (default order)

/api/v1/events/

GETPOSTPUTPATCH

• Filters slug event_type is_online is_featured
• search title description location
• ordering start_date title updated_at (default -start_date)

/api/v1/jobs/

GETPOSTPUTPATCH

• Filters slug category__slug contract_type remote_option experience_level is_featured is_urgent
• search title description location skills_required
• ordering published_date title updated_at (default -published_date)

/api/v1/faq/

GETPOSTPUTPATCH

• Filters category__slug is_featured
• search question answer
• ordering order updated_at (default order)

/api/v1/bookable-items/

GET

/api/v1/bookings/

POST

Security recommendations#

• Keep keys on your server. Never ship a key in a mobile app or in browser code.
• Use a read key wherever you do not need to write.
• One key per integration: revoking one does not break the others.