The candidates API manages job-seeker profiles on the platform. Candidates store their personal details, education level, skills, work experience, and a CV document that is required before applying to any vacancy. Companies can also retrieve a candidate’s profile when reviewing an application.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Esteban-Mendez-j/Proyecto-Docker/llms.txt
Use this file to discover all available pages before exploring further.
CandidatoDTO fields
CandidatoDTO extends UsuarioDTO and inherits the base user fields listed below in addition to its own.
Inherited from UsuarioDTO
Unique user ID.
First name. Max 50 characters.
Email address (unique). Max 100 characters.
Password. Required on creation only. Max 15 characters. Not returned on reads.
Phone number (unique). Max 15 characters.
Personal bio or summary. Max 400 characters.
Profile image file path. Required on creation. Max 255 characters.
Account registration date.
Date of last login.
Whether the account is active.
Roles assigned to the user (e.g.
["CANDIDATO"]).Administrative note on the account.
Last name. Max 20 characters.
National identification number (unique). Max 11 characters.
Highest education level (e.g.
"Universitario", "Técnico"). Max 30 characters.Years of professional experience (e.g.
"3"). Max 4 characters.List of skills. Used by the ML model to rank vacancy matches.
File path to the uploaded CV (PDF). Must be present before applying to any vacancy. Max 225 characters.
Path to an optional personal presentation video. Max 255 characters.
Endpoints
Get candidate profile
Returns the full profile of a candidate, including their education history and work history. WhenidUsuario is not supplied, the ID is extracted from the JWT token. Companies can pass nPostulacion to view the profile of an applicant — the server verifies that the application belongs to the specified user before returning data.
The
jwtToken cookie is required when idUsuario is not provided in the query string. If neither is present the server returns 401 Unauthorized.User ID of the candidate to retrieve. When omitted, the ID is read from the JWT token.
Application ID. When provided along with a company token, the server validates that the application belongs to the candidate before serving the profile.
401— No session token provided or token expired.403— Company tried to access a profile not linked to one of their applications.404— Candidate not found.
Create candidate profile
Creates a new candidate record. Typically called automatically during the registration flow.application/json — CandidatoDTO
Required fields: nombre, apellido, correo, imagen.
Get candidate by ID
Returns the rawCandidatoDTO for a specific user ID. Used for populating edit forms.
User ID of the candidate.
CandidatoDTO object.
Update candidate profile
Updates candidate data including an optional profile image and a required CV file. Usesmultipart/form-data to support file uploads. If an image or CV already exists, the server deletes the old file before saving the new one.
User ID of the candidate to update. Must match
candidatoDTO.idUsuario in the request body.multipart/form-data
Updated candidate data serialised as JSON.
Optional new profile image. When provided, replaces any existing image.
The candidate’s CV in PDF format. Must be provided on every update call.
Delete candidate
Permanently removes a candidate record from the system.ID of the candidate to delete.
204 No Content.
Example