# Amtrak Stations API

> Amtrak: all 1,031 rail stations and Thruway bus stops with codes, cities, states and accessibility

- Vendor: `amtrakstationsapi` · version 1.0 · category Transport · tags amtrak api, amtrak stations api, us rail stations api, train station codes api, passenger rail api, station accessibility api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/amtrakstationsapi
- This document: https://apiclay.com/docs/amtrakstationsapi.md
- OpenAPI 3.1: https://apiclay.com/api/amtrakstationsapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `amtrakstationsapi`
- Updated: 2026-11-18

## About

## Amtrak Stations API

The station reference data behind Amtrak's booking site: every station and Thruway bus stop it sells tickets to, in the US and Canada, with its three-letter code, name, city, state and time zone; and for each station code whether it is staffed, accessible, has wheelchair assistance and supports Quik-Trak ticket machines.

Data comes from **amtrak.com** (https://www.amtrak.com). Every route calls the source's own public API and returns it unchanged.

Typical flow: `POST /stations` for every station `code`, then `POST /station-info` for staffing and accessibility by code.

### Routes

#### POST `/stations` - Stations
No parameters.

Returns: Array of 1,031 stations: `code` (e.g. `NYP`), `name`, `stationName32`, `autoFillName`, `city`, `state`, `timezone` (`E`, `C`, `M`, `P`...).

#### POST `/station-info` - Station info
No parameters.

Returns: `stations` array: `stationCode`, `staffed`, `stationAccessible`, `wheelChairAvailable`, `quikTrakAvailable`.

### Caveats

- Station lists change with timetables; refresh them rather than caching for long.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by amtrak.com.

## Pricing

- Pay as you go: 0.01 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### POST /stations — Stations
- Gateway: `POST https://api.apiclay.com/v1/api/amtrakstationsapi/stations`
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### POST /station-info — Station info
- Gateway: `POST https://api.apiclay.com/v1/api/amtrakstationsapi/station-info`
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X POST "https://api.apiclay.com/v1/api/amtrakstationsapi/stations" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

Index of every published API: https://apiclay.com/llms.txt
