---
title: "Boost Itinerary"
method: POST
path: "/admin/itineraries/{itinerary_id}/boost"
tags: ["admin"]
---

# Boost Itinerary

`POST /admin/itineraries/{itinerary_id}/boost`

## 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}/boost`
- Auth: none declared

Activate a scan-boost across EVERY leg of a route, atomically.

Boosting a route one leg at a time is not a slower version of this — it
is useless.  The aggregator is level-triggered and fires only when all N
nights stand open simultaneously, so the route's detection latency equals
that of its slowest-polling leg.  Speeding up leg 2 while legs 1 and 3
stay at tier cadence leaves the route exactly as slow as before, at 3x
the poll cost of doing nothing.  Hence one lever for the whole route.

Same 30–45s band and provider gate as the per-alert boost: rejected
unless every provider the route's legs touch is boost-eligible
(``Platform.allows_scan_boost``).

## Path parameters

- `itinerary_id` string, required

## Response `200`

Successful Response

- unknown

## 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)