Skip to main content
This page documents every HTTP route available to users with the Speaker (Ponente) or Participant role in SIGEP. Speaker routes are defined in ponente/urls.py and mounted under /ponente/. Participant routes are defined in participante/urls.py and mounted under /participante/.
Each role has its own isolated route group. Speaker routes require the PONENTE role and participant routes require the PARTICIPANTE role. Requests from users without the matching role will be rejected.

Speaker routes

MethodPathDescription
GET/ponente/Speaker panel. Displays a summary of your current event participation.
GET/ponente/panel/Speaker panel alias. Renders the same view as /ponente/.
GET, POST/ponente/inscripcion/Event registration page. A GET request displays the registration form; a POST request submits it.
GET, POST/ponente/participacion/Manage your participation and uploaded documents. A GET request displays current submissions; a POST request saves changes.
/ponente/ and /ponente/panel/ are served by the same panel view. The root path is registered under the name dashboard and /ponente/panel/ is registered under the name panel.

Participant routes

MethodPathDescription
GET/participante/Participant panel. Displays a summary of your event enrollments and project status.
GET/participante/panel/Participant panel alias. Renders the same view as /participante/.
GET/participante/evento/elegir/Displays the list of available events so you can choose one to register for.
POST/participante/evento/<pk>/eliminar/Removes your registration for the project identified by pk.
/participante/ and /participante/panel/ are served by the same panel_participante view. Both names (panel_participante and panel) resolve to the same page.
The /participante/evento/<pk>/eliminar/ route permanently removes your project registration. This action cannot be undone from the participant interface.

Build docs developers (and LLMs) love