Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Manuelfg1985/Proyecto_Final_26/llms.txt

Use this file to discover all available pages before exploring further.

The /up endpoint returns the current server status along with a confirmation message. It is designed for uptime monitoring, load balancer health probes, or any automated check that needs to verify the Agencia de Habilidades para el Futuro API is reachable and running. No authentication is required to call this endpoint.

Method & Path

FieldValue
MethodGET
Path/up
AuthNone

Response

200 OK

A successful request returns an HTTP 200 OK with the following JSON body:
{
  "status": "ok",
  "message": "Servidor activo"
}
status
string
required
Always "ok" when the server is running and able to handle requests.
message
string
required
A human-readable confirmation string. Always "Servidor activo" (Spanish for “Server active”).

Example

Send a GET request to the health check endpoint:
curl https://proyecto-final-26-6tn2.vercel.app/up
Expected response:
{
  "status": "ok",
  "message": "Servidor activo"
}
When running locally, replace the base URL with http://localhost:3000. The endpoint and response are identical in both environments.

404 Handler

Any request to a route that does not exist in the API is caught by the global 404 handler defined at the end of index.js. It returns an HTTP 404 Not Found with the following body:
{
  "error": "Ruta no encontrada"
}
This handler acts as a catch-all for unmatched routes and ensures every request receives a structured JSON error rather than an unhandled Express default response.
Add https://proyecto-final-26-6tn2.vercel.app/up to your monitoring tool (such as UptimeRobot, Better Uptime, or Checkly) or include a curl call to it as a post-deploy step in your CI/CD pipeline. A 200 response with "status": "ok" confirms the deployment is live and the server is accepting requests.

Build docs developers (and LLMs) love