Skilzy API for training organisations

The Skilzy REST API lets your organisation automatically pull your learners' data (activity, attendance, evaluations, documents, satisfaction) into your own tools: Airtable, spreadsheets, ETL, BI. Mostly read; a write operation also lets you enrol a learner (key with the “write” scope). Scoped to your organisation. These are the same figures as the PDF binders.

Quickstart

Three steps to your first call:

Generate an API key from the “API & integrations” page in your dashboard (it starts with sk_live_).

Make your first call, passing the key in the Authorization header:

curl -H "Authorization: Bearer sk_live_xxx" \
  "https://skilzy.io/api/v1/learners?limit=100"

You get a JSON response: rows are in data, with pagination in pagination.

{
  "resource": "learners",
  "meta": { "org_name": "Mon OF", "year": 2026, "generated_at": "..." },
  "pagination": { "limit": 100, "offset": 0, "count": 42, "total": 42, "has_more": false },
  "data": [
    { "nom": "Jean Dupont", "email": "jean@…", "temps_actif_min": 184, "evaluations_reussies": 12, … }
  ]
}

Authentication

Every request must carry an organisation API key in the HTTP header. Create and manage your keys from the “API & integrations” page in your dashboard.

Authorization: Bearer sk_live_xxxxxxxxxxxxxxxx

The key is shown only once at creation; copy it right away.
A key only grants access to your organisation's data.
You can revoke a key at any time; it then returns a 401 error.
A key can have an expiry date (set at creation). After that date it returns 401 “API key expired”; generate a new one.
Never expose a key in a browser / public front-end.

Endpoints

Base URL: https://skilzy.io/api/v1

All resources are queried with GET:

Endpoint	Content
GET /api/v1/learners	Per-learner summary (1 row / learner)
GET /api/v1/users	Org learners + assigned license (1 row / learner)
GET /api/v1/summary	Counters: learners + licenses by type (single object in data, not an array)
GET /api/v1/attendance	Tutoring attendance (1 row / learner × session)
GET /api/v1/evaluations	Quiz attempts (1 row / attempt)
GET /api/v1/quiz-answers	Quiz answers question by question (1 row / attempt × question)
GET /api/v1/documents	Issued PIF & certificates (1 row / document)
GET /api/v1/satisfaction	Satisfaction surveys (1 row / survey)
GET /api/v1/enrollments	Progress per learner × programme (1 row / enrolment)
GET /api/v1/progress	Detailed progress (1 row / learner × programme × lesson)
GET /api/v1/logins	Timestamped logins (1 row / login)
GET /api/v1/tutoring-ratings	Tutoring ratings (session + trainer) (1 row / rating)
GET /api/v1/lesson-ratings	Milestone / module-end lesson ratings (1 row / rating)

Query parameters

Parameter	Description	Default
format	Output format: json or csv	json
year	Filtered calendar year (e.g. 2026)	Current year
limit	Rows per page (max 1000, JSON)	100
offset	Pagination offset (JSON)	0
updated_since	Only rows whose date ≥ value (YYYY-MM-DD). Incremental sync. Ignored for learners.	—
email	Restricts to ONE learner (exact email, case-insensitive). 404 if unknown in your organisation.	—
user_id	Like email, but by the learner's technical identifier.	—
programme	Restricts to ONE programme (programme slug, e.g. marketing-contenus-rs7439). Ignored on resources without a programme (learners, logins).	—

Single-learner requests (email or user_id) are served through a direct path: they are not affected by the org-wide aggregation cap (meta.truncated) and return a meta.learner block.

# Un seul apprenant (toutes les ressources acceptent ?email= ou ?user_id=)
curl -H "Authorization: Bearer sk_live_xxx" \
  "https://skilzy.io/api/v1/learners?email=jean@orga.fr"

# Son avancement sur UNE formation (première/dernière connexion incluses)
curl -H "Authorization: Bearer sk_live_xxx" \
  "https://skilzy.io/api/v1/enrollments?email=jean@orga.fr&programme=marketing-contenus-rs7439"

# Ses réponses de quiz, question par question
curl -H "Authorization: Bearer sk_live_xxx" \
  "https://skilzy.io/api/v1/quiz-answers?email=jean@orga.fr"

Response format

JSON responses contain metadata, pagination and rows in data:

{
  "resource": "learners",
  "meta": { "org_name": "Mon OF", "year": 2026, "generated_at": "..." },
  "pagination": { "limit": 100, "offset": 0, "count": 42, "total": 42, "has_more": false },
  "data": [
    { "nom": "Jean Dupont", "email": "jean@…", "temps_actif_min": 184, "evaluations_reussies": 12, … }
  ]
}

With ?format=csv, the response is a downloadable CSV file (UTF-8 with BOM, comma-separated), without pagination.

Exception: the summary resource returns a single object in data (not an array) and has no pagination:

{
  "resource": "summary",
  "meta": { "org_name": "Mon OF", "generated_at": "2026-06-10T09:00:00.000Z" },
  "data": {
    "utilisateurs": { "total": 38, "actifs": 31 },
    "licences": {
      "standard": { "total": 50, "disponibles": 12, "utilisees": 38 },
      "tutorat":  { "total": 10, "disponibles": 4,  "utilisees": 6 }
    }
  }
}

Field reference

JSON keys are always in French regardless of language. Boolean values are returned as “Oui” / “Non”.