# NTS Radio Live Schedule API

> NTS Radio's two live channels: what is on now and next, plus the archive of resident and guest shows

- Vendor: `ntsradiolivescheduleapi` · version 1.0 · category Music · tags nts radio api, radio schedule api, live radio api, music shows api, dj mixes api, now playing api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/ntsradiolivescheduleapi
- This document: https://apiclay.com/docs/ntsradiolivescheduleapi.md
- OpenAPI 3.1: https://apiclay.com/api/ntsradiolivescheduleapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `ntsradiolivescheduleapi`
- Updated: 2026-11-18

## About

## NTS Radio Live Schedule API

Data from NTS, the London-based online radio station: the show on air now and the upcoming schedule on channels 1 and 2 (title, times, description, genres, location, artwork), and a paged list of NTS shows.

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

Typical flow: `/live` for what is on now, `/shows?offset=0&amp;limit=12` to browse shows.

### Routes

#### GET `/live` - Live schedule
No parameters.

Returns: `results[]` per channel with `channel_name`, `now` and `next1`...`next17` (`broadcast_title`, `start_timestamp`, `end_timestamp`, `embeds.details` with `description`, `genres`, `location_long`, `media`).

#### GET `/shows` - Shows
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| offset | query | number | no | Offset. |
| limit | query | number | no | Shows per page. |

Returns: `metadata.resultset.count` and `results[]` with `name`, `description`, `show_alias`, `genres`, `media`.

### Caveats

- Schedule text and artwork belong to NTS and its artists.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by nts.live.

## Pricing

- Pay as you go: 0.0012 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.

### GET /live — Live schedule
- Gateway: `GET https://api.apiclay.com/v1/api/ntsradiolivescheduleapi/live`
- 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.

### GET /shows — Shows
- Gateway: `GET https://api.apiclay.com/v1/api/ntsradiolivescheduleapi/shows`
- Public query params: `offset` (number), `limit` (number)
- 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 GET "https://api.apiclay.com/v1/api/ntsradiolivescheduleapi/live" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

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