Creating a project is an atomic operation backed by theDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/Taykl12/Classify/llms.txt
Use this file to discover all available pages before exploring further.
create_grupo_proyecto database RPC. The RPC inserts a row into grupos_proyectos and immediately links the authenticated user as the project owner in proyecto_profesor — both in a single transaction, so there is no window where a project exists without an owner. After the RPC returns, any provided memberEmails are synced into grupo_estudiante. Every email in that list must already exist in the system; a single unrecognised address causes the entire request to fail with a 400.
Endpoint
Request
Headers
| Header | Value |
|---|---|
Authorization | Bearer <token> |
Content-Type | application/json |
Body Parameters
Display name for the new project. Must be a non-empty string. Stored in
nombre_proyecto.Optional short description of the project. Stored in the project’s description field.
Optional list of student email addresses to enroll as members on creation. Every address must correspond to an existing user in
sistema; any unknown address causes a 400 and the entire request is rolled back.Example Request
Response
Returns 201 Created with a project list item extended with thememberEmails array.
Response Fields
Newly assigned project identifier.
Project name as stored.
Short description. Empty string (
"") if none was provided.All newly created projects begin in the
"Abierto" state.false for all newly created projects.Creation date formatted as
DD/MM/YYYY (e.g. "20/11/2024"), derived from the database timestamp.Supplementary scope notes. Always
"" for a newly created project.Pre-project validation flag. Always
false for a newly created project.The resolved list of member emails enrolled during creation. Mirrors the
memberEmails input when all addresses were valid.Example Response
Error Responses
| Status | Description |
|---|---|
400 Bad Request | name was not provided or was empty. |
400 Bad Request | One or more emails in memberEmails do not correspond to an existing user. The response body identifies the unrecognised addresses. |
401 Unauthorized | Missing or invalid bearer token. |