How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

EPFL Memento Events API

EPFL's public events and agenda API, serving the Memento calendar — events, mementos, registrations, domains, categories, faculties, spoken languages and vulgarizations. Django REST Framework, read-only and unauthenticated by default, documented as an interactive CoreAPI schema. Note that Memento and Actu share a resource vocabulary but not a resource set: only /categories/ and /faculties/ answer on both hosts. The repo previously pointed every derived contract at actu.epfl.ch, including six resources actu.epfl.ch 404s on; that was corrected on 2026-08-19 by probing all thirteen collections against both hosts.

EPFL Memento Events API is one of 9 APIs that EPFL publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Event, Calendar, and University. The published artifact set on APIs.io includes API documentation, an OpenAPI specification, sample payloads, and 1 JSON Schema.

This API exposes 17 operations across 17 paths, and defines 16 schemas. It is described by OpenAPI 3.0.3, at version v1.

Requests are made against a single base URL, https://memento.epfl.ch/api/v1.

17 operations 17 paths 16 schemas 17 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
v1
Base URL
https://memento.epfl.ch/api/v1/
Authentication
API Key, HTTP Basic
Resource Areas
1

Authentication & Security 2

EPFL Memento Events API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (tokenAuth). It accepts HTTP basic authentication (basicAuth).

  • tokenAuth — Optional DRF Token authentication.

Paths & Operations 17

Across 17 paths, the API surfaces 17 operations — 17 GET. Each is listed below with its method, path, parameters, and response codes.

Operations 17
GET
/categories/
List all Category objects.
listCategories 4 params → 200
GET
/categories/{id}/
Return the details about the given Category id.
readCategory 3 params → 200
GET
/domains/
List all Domain objects.
listDomains 4 params → 200
GET
/domains/{id}/
Return the details about the given Domain id.
readDomain 3 params → 200
GET
/events/
List all Event objects with filtering.
listEvents 24 params → 200
GET
/events/{event__pk}/
Return the details about the given Event id.
readEvent 3 params → 200
GET
/faculties/
List all Faculty objects.
listFaculties 4 params → 200
GET
/faculties/{id}/
Return the details about the given Faculty id.
readFaculty 3 params → 200
GET
/mementos/
List all Memento objects.
listMementos 4 params → 200
GET
/mementos/{id}/
Return the details about the given Memento id.
readMemento 3 params → 200
GET
/mementos/{id}/events/
List events for a memento.
listMementoEvents 1 param → 200
GET
/registrations/
List all Registration objects.
listRegistrations → 200
GET
/registrations/{id}/
Return the details about the given Registration id.
readRegistration 1 param → 200
GET
/spoken_languages/
List all Spoken Language objects.
listSpokenLanguages 4 params → 200
GET
/spoken_languages/{id}/
Return the details about the given Spoken Language id.
readSpokenLanguage 3 params → 200
GET
/vulgarizations/
List all Vulgarization objects.
listVulgarizations → 200
GET
/vulgarizations/{id}/
Return the details about the given Vulgarization id.
readVulgarization 1 param → 200

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are Event (38 properties), PaginatedSpokenLanguageList (4 properties), PaginatedMementoList (4 properties), PaginatedFacultyList (4 properties). Each schema is shown below with its type and property counts.

Category
object
2 properties
Domain
object
2 properties
Faculty
object
2 properties
Memento
object
2 properties
SpokenLanguage
object
2 properties
Vulgarization
object
2 properties
Registration
object
2 properties
Event
object
38 properties
PaginatedEventList
object
4 properties
PaginatedCategoryList
object
4 properties
PaginatedDomainList
object
4 properties
PaginatedFacultyList
object
4 properties
PaginatedMementoList
object
4 properties
PaginatedSpokenLanguageList
object
4 properties
PaginatedRegistrationList
object
4 properties
PaginatedVulgarizationList
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

epfl-memento.yaml Raw ↑

Other APIs EPFL publishes across the network.

EPFL Actu News API
EPFL Infoscience Institutional Repository
EPFL Graph Search
EPFL go.epfl.ch URL Shortener API
EPFL SAML Identity Federation Entities
EPFL Identity Provider (SWITCH edu-ID, tenant)
EPFL Library Discovery on swisscovery (Ex Libris, tenant)
EPFL Primers API
Where this information came from

This is an independent, third-party profile of EPFL Memento Events API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.