Look up sector

Returns the fare sector for a given neighborhood name. Useful for understanding which pricing tier applies before calling /calculate-fare.

Endpoint

GET /api/v2026/sector

Caching: Responses include Cache-Control: public, max-age=300.

Query parameters

barrio

string

required

The neighborhood name to look up. Matching is exact after normalizing accents and casing — "San Fernando", "san fernando", and "SAN FERNANDO" all resolve to the same result.

Response

200 — Sector found

success

boolean

required

Always true on a successful response.

timestamp

string

required

ISO 8601 UTC timestamp of the response.

data

object

required

Hide properties

barrio

string

The neighborhood name as provided in the query parameter.

sector

string

Human-readable sector label (e.g., "primer sector", "cuarto sector", "tarifa especial").

fuente

string

Which table the neighborhood was found in: "general" (standard fare table) or "terminal" (Terminal de Transporte fare table). A neighborhood can exist in both tables with different sectors — see the fare calculation logic.

Error responses

HTTP status	Error code	Cause
`400`	`MISSING_PARAM`	`barrio` query parameter was not provided.
`404`	`BARRIO_NOT_FOUND`	The neighborhood was not found in any table.

Examples

curl "http://localhost:3000/api/v2026/sector?barrio=San%20Fernando"

Sample response — found

{
  "success": true,
  "timestamp": "2026-03-10T14:30:00.000Z",
  "data": {
    "barrio": "San Fernando",
    "sector": "primer sector",
    "fuente": "general"
  }
}

Sample response — not found

{
  "success": false,
  "timestamp": "2026-03-10T14:30:00.000Z",
  "error": {
    "code": "BARRIO_NOT_FOUND",
    "message": "Barrio \"BarrioFalso\" no encontrado"
  }
}

Overview

Endpoints

Endpoint

Query parameters

Response

200 — Sector found

Error responses

Examples

Sample response — found

Sample response — not found

Build docs developers (and LLMs) love

Overview

Endpoints

​Endpoint

​Query parameters

​Response

​200 — Sector found

​Error responses

​Examples

​Sample response — found

​Sample response — not found

Build docs developers (and LLMs) love

Endpoint

Query parameters

Response

200 — Sector found

Error responses

Examples

Sample response — found

Sample response — not found