Skip to main content
POST
/
api
/
route-calls
/
:routeCallId
/
attendances
curl -X POST https://api.losinmaduros.com/api/route-calls/987e6543-e21b-12d3-a456-426614174000/attendances \
  -H "Authorization: Bearer YOUR_TOKEN"

{
  "success": true,
  "data": {
    "id": "123e4567-e89b-12d3-a456-426614174000",
    "userId": "user_2abc123def456",
    "routeCallId": "987e6543-e21b-12d3-a456-426614174000",
    "status": "CONFIRMED",
    "createdAt": "2026-02-10T10:00:00Z",
    "updatedAt": "2026-02-10T10:00:00Z",
    "user": {
      "id": "user_2abc123def456",
      "name": "John",
      "imageUrl": "https://example.com/avatar.jpg"
    },
    "routeCall": {
      "id": "987e6543-e21b-12d3-a456-426614174000",
      "title": "Ruta Casa de Campo - Domingo",
      "dateRoute": "2026-02-15T10:00:00Z",
      "pace": "MARIPOSA",
      "status": "SCHEDULED"
    }
  },
  "message": "Attendance confirmed successfully"
}
Confirm your attendance to a specific route call. If you previously cancelled your attendance, this endpoint will reactivate it.

​
Authentication

This endpoint requires authentication. Include a valid Bearer token in the Authorization header.

​
Path Parameters

​
routeCallId
string
required
The unique identifier (UUID) of the route call to attend.Example: 987e6543-e21b-12d3-a456-426614174000

​
Behavior

  • If this is your first time confirming attendance, a new attendance record with status CONFIRMED will be created
  • If you previously cancelled your attendance, it will be reactivated and status updated to CONFIRMED
  • Cannot confirm attendance for route calls with status CANCELLED or COMPLETED
  • Cannot confirm if you already have a CONFIRMED attendance for this route call

​
Response

​
success
boolean
Indicates if the request was successful.Example: true
​
data
object
The attendance object
​
message
string
A success message.Example: Attendance confirmed successfully

​
Status Codes

​
201
Created
Attendance confirmed successfully.
​
400
Bad Request
Cannot attend cancelled or completed route calls.Example errors:
  • Cannot attend a cancelled route call
  • Cannot attend a completed route call
​
401
Unauthorized
Invalid or missing authentication token.
​
404
Not Found
Route call not found.
​
409
Conflict
You are already attending this route call.
curl -X POST https://api.losinmaduros.com/api/route-calls/987e6543-e21b-12d3-a456-426614174000/attendances \
  -H "Authorization: Bearer YOUR_TOKEN"

{
  "success": true,
  "data": {
    "id": "123e4567-e89b-12d3-a456-426614174000",
    "userId": "user_2abc123def456",
    "routeCallId": "987e6543-e21b-12d3-a456-426614174000",
    "status": "CONFIRMED",
    "createdAt": "2026-02-10T10:00:00Z",
    "updatedAt": "2026-02-10T10:00:00Z",
    "user": {
      "id": "user_2abc123def456",
      "name": "John",
      "imageUrl": "https://example.com/avatar.jpg"
    },
    "routeCall": {
      "id": "987e6543-e21b-12d3-a456-426614174000",
      "title": "Ruta Casa de Campo - Domingo",
      "dateRoute": "2026-02-15T10:00:00Z",
      "pace": "MARIPOSA",
      "status": "SCHEDULED"
    }
  },
  "message": "Attendance confirmed successfully"
}

Build docs developers (and LLMs) love

Get started for freeTalk to us