---
title: "Itinerary Detail"
method: GET
path: "/admin/itineraries/{itinerary_id}"
tags: ["admin"]
---

# Itinerary Detail

`GET /admin/itineraries/{itinerary_id}`

## Request

- Base URL: `https://api.alert.camp` (the document declares no server; this is the origin it was published from)
- URL: `https://api.alert.camp/admin/itineraries/{itinerary_id}`
- Auth: none declared

Route parent detail: its legs, its openings, and the route-wide boost.

The three things an alert page structurally cannot show for a route:
the parent's own window/sweep state, the legs as an ordered set rather
than N unrelated alerts, and the ``itinerary_openings`` rows that are the
route's real output (legs persist ``AlertMatch`` rows, but a leg match is
not a route opening — the aggregator emits for the parent).

## Path parameters

- `itinerary_id` string, required

## Response `200`

Successful Response

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/alert/apis/alertcamp.md) · [All operations](https://skmtc.dev/alert/apis/alertcamp/llms.txt) · [OpenAPI document](https://skmtc.dev/alert/apis/alertcamp/revisions/864c8c9ef833?raw)