> ## Documentation Index
> Fetch the complete documentation index at: https://docs.truckaurbus.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Launches

> Every launch of a truck, bus, construction machine or tractor in India by the maker's launch day, with what changed against the model before it.

The launch tracker reads the register by the day each maker launched a model, not the day it reached the register. The same key and scope that read vehicles, machines and tractors (`catalogue:read`) read it, and each call is a standard call.

## What a launch is

A launch is one model, or one vehicle range. A range is the vehicles of one maker whose names share the words before the first figure: the Starbus Prime 24+D and the Starbus Prime 40+D are the Starbus Prime range. The builds of one range launched within seven days of the range's first day count as one launch, with the build count and every build listed. A construction machine, a tractor or a farm machine is its own launch.

A launch carries an `id` such as `v-tata-motors-starbus-prime-2026-07-09` (vehicles), `m-beml-bh60-ev-2026-09-30` (construction machines) or `f-mahindra-tractors-475-di-ms-xp-plus-2026-10-21` (the field), and:

* `kind` (`vehicle`, `machine` or `farm`), `launched_on`, the `maker`, the `name` (the range's, or the model's), `is_range` and `builds`
* `class_key` and `class_label`, `fuels` and `electric`
* `price_from` with its `kind` (`maker` is ex-showroom, `dealer`, `reported` is a band reported in public, `estimate`) and `as_of`; show the kind beside the figure, as the [Prices](https://docs.truckaurbus.com/guides/prices.md) guide asks
* `figures`: the launch's own figures, each with its unit and, for a range, the highest beside the lowest
* `changed`: what changed against the model it `replaces` or sits `beside`, row by row (`now`, `was`, `change`, `same`; the price rows carry each figure's kind). `null` until the pair is set; `new_to_range` when the model is new to its maker's range
* `first_from_maker`: the maker's first launch on the register
* `path`: the page on truckaurbus.com

## The timeline

`GET /v1/launches?since=&until=&kind=&maker=&class=&fuel=&electric=&limit=&cursor=` answers newest first. `since` and `until` are days (`YYYY-MM-DD`); without them the answer is the last 180 days. `kind` takes `vehicle`, `machine` or `farm`, or a comma list. `class` is a vehicle class (`truck`, `bus`, `pickup`, `three-wheeler`, `tractor`, `tipper`) or a machine class (`excavator`, `backhoe-loader`, `tractor`, `agri-drone` and the rest). `limit` is at most 100. When there is more, `next_cursor` is set: pass it as `cursor` for the next page.

```bash theme={"system"}
curl "https://api.truckaurbus.com/v1/launches?since=2026-05-01&kind=machine&electric=true" \
  -H "Authorization: Bearer tab_live_..."
```

## One launch

`GET /v1/launches/{id}` is one launch with every build under `rows` (slug, name, page, fuel, lifecycle and each build's price from).

## The season

`GET /v1/launches/season?since=&until=` counts the window: launches and builds, `by_kind`, `by_month` (each kind), `by_maker` (launches and builds), `by_class` (launches and the electric ones), `electric`, `hybrid` and `electric_by_kind`.

## Coming next

`GET /v1/launches/coming?kind=` lists the models a maker has announced that are not on sale yet. Each one carries the maker's own words for when (`timing.en`, with `hi` and `ta` where we hold them) and the month, where the maker named one. It is never our estimate. An empty list is a real answer: nothing announced is waiting.

## Calls and prices

Each launch door is a standard call. A list that comes back empty is not charged, and nor is a launch we do not hold (404). See [Limits](https://docs.truckaurbus.com/limits.md).

## MCP

The hosted MCP server has three tools: `launches` (the timeline with the same filters), `launch` (one launch) and `launches_coming`. See [MCP](https://docs.truckaurbus.com/guides/mcp.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.