---
title: "Calendar Fares Get"
method: GET
path: "/api/calendar/fares"
tags: ["calendar"]
---

# Calendar Fares Get

`GET /api/calendar/fares`

## Request

- Base URL: `https://api.pointifytravels.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.pointifytravels.com/api/calendar/fares`
- Auth: none declared

Fast read-only calendar view of fares for a route + date window.

Returns whatever is already in the cache and kicks off a background
warm for misses. The POST /calendar/search SSE endpoint is still
the right path when a client wants live scraper results streamed
as they arrive; this GET exists for the marketing calendar page
which needs a snappy non-streaming response and is happy to show
dashes for uncached days.

Response shape matches what the Next.js route at
apps/web/src/app/api/calendar/fares/route.ts already expects, so
the web side is a pure pass-through.

## Query parameters

- `origin` string, required
- `destination` string, required
- `start_date` string, required
- `end_date` string, required
- `cabin` string
- `search_type` string

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/pointifytravels/apis/pointify-deal-engine.md) · [All operations](https://skmtc.dev/pointifytravels/apis/pointify-deal-engine/llms.txt) · [OpenAPI document](https://skmtc.dev/pointifytravels/apis/pointify-deal-engine/revisions/4350142a4216?raw)