Skip to main content
Authentication is optional when fetching a profile by UUID. However, using me as the id requires an authenticated session — the endpoint returns 401 if no session is found.

Path parameters

id
string
required
UUID of the profile to retrieve. Pass me to return the profile of the currently authenticated user.

The “me” shortcut

When you pass me as the id, the server resolves it to the authenticated user’s own UUID before querying the database. This is equivalent to calling GET /api/perfil/{your-uuid} but without needing to know your UUID in advance.
GET /api/perfil/me returns 401 if the request is made without a valid authenticated session.

Response fields

id
string
required
UUID of the profile.
nombre
string
required
Display name of the user.
avatar_url
string
URL of the user’s avatar image. May be null.
sobre_mi
string
Short bio written by the user. May be null.
bloqueado
boolean
required
Whether the account is blocked by an administrator.
is_admin
boolean
required
Whether this user has administrator privileges.
isOwnProfile
boolean
required
true when the authenticated user is viewing their own profile. Always false for unauthenticated requests.
currentUserIsAdmin
boolean
required
true when the currently authenticated user has administrator privileges. Always false for unauthenticated requests.

Examples

curl --request GET \
  --url 'https://yourdomain.com/api/perfil/a1b2c3d4-e5f6-7890-abcd-ef1234567890'

200 — success

{
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "nombre": "María García",
  "avatar_url": "https://example.com/avatars/maria.png",
  "sobre_mi": "Amante de la cocina tradicional.",
  "bloqueado": false,
  "is_admin": false,
  "isOwnProfile": true,
  "currentUserIsAdmin": false
}

401 — unauthenticated “me” request

{
  "error": "No autorizado o ID no proporcionado"
}

404 — profile not found

{
  "error": "Perfil no encontrado"
}

500 — internal server error

{
  "error": "Error interno del servidor"
}

Build docs developers (and LLMs) love