---
name: tv-api
description: "TV API skill. Use when working with TV for platform, channel, asset. Covers 18 endpoints."
version: 1.0.0
generator: lapsh
---

# TV API
API version: 2.0

## Auth
ApiKey apikey in header

## Base URL
https://tv.api.pressassociation.io/v2

## Setup
1. Set your API key in the appropriate header
2. GET /platform -- platform collection
3. Explore available endpoints below

## Endpoints
18 endpoints across 8 groups. See references/api-spec.lap for full details.

### Platform
| Method | Path | Description |
|--------|------|-------------|
| GET | /platform | Platform Collection |
| GET | /platform/{platformId} | Platform Detail |
| GET | /platform/{platformId}/region | Platform Region Collection |

### Channel
| Method | Path | Description |
|--------|------|-------------|
| GET | /channel | Channel Collection |
| GET | /channel/{channelId} | Channel Detail |

### Asset
| Method | Path | Description |
|--------|------|-------------|
| GET | /asset | Asset Collection |
| GET | /asset/{assetId} | Asset Detail |
| GET | /asset/{assetId}/contributor | Asset Contributors |

### Contributor
| Method | Path | Description |
|--------|------|-------------|
| GET | /contributor | Contributor Collection |
| GET | /contributor/{contributorId} | Contributor Detail |

### Schedule
| Method | Path | Description |
|--------|------|-------------|
| GET | /schedule | Schedule Collection |

### Feature-type
| Method | Path | Description |
|--------|------|-------------|
| GET | /feature-type | Feature Type Collection |

### Feature
| Method | Path | Description |
|--------|------|-------------|
| GET | /feature | Feature Collection |
| GET | /feature/{featureId} | Feature Detail |

### Catalogue
| Method | Path | Description |
|--------|------|-------------|
| GET | /catalogue | Catalogue Collection |
| GET | /catalogue/{catalogueId} | Catalogue Detail |
| GET | /catalogue/{catalogueId}/asset | Catalogue Asset Collection |
| GET | /catalogue/{catalogueId}/asset/{assetId} | Catalogue Asset Detail |

## Common Questions
Match user requests to endpoints in references/api-spec.lap. Key patterns:
- "List all platform?" -> GET /platform
- "Get platform details?" -> GET /platform/{platformId}
- "List all region?" -> GET /platform/{platformId}/region
- "List all channel?" -> GET /channel
- "Get channel details?" -> GET /channel/{channelId}
- "List all asset?" -> GET /asset
- "Get asset details?" -> GET /asset/{assetId}
- "List all contributor?" -> GET /asset/{assetId}/contributor
- "Get contributor details?" -> GET /contributor/{contributorId}
- "List all schedule?" -> GET /schedule
- "List all feature-type?" -> GET /feature-type
- "List all feature?" -> GET /feature
- "Get feature details?" -> GET /feature/{featureId}
- "List all catalogue?" -> GET /catalogue
- "Get catalogue details?" -> GET /catalogue/{catalogueId}
- "How to authenticate?" -> See Auth section above

## Response Tips
- Check response schemas in references/api-spec.lap for field details
- Paginated endpoints accept limit/offset or cursor parameters

## References
- Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas

> Generated from the official API spec by [LAP](https://lap.sh)