canonical: https://jentic.com/apis/helipaddy.com/helipaddy

# Helipaddy Sites API

Jentic publishes the only available OpenAPI specification for Helipaddy Sites API, keeping it validated and agent-ready. Helipaddy maintains a directory of helicopter and passenger-drone landing sites with location, contact, and operational details. The Sites API lets pilots, operators, and aviation apps look up sites by id, list sites in a region, and find the nearest landing pads to a given coordinate. Authentication is by bearer token issued via the auth/login endpoint, with usage statistics available on /usage.

## For AI agents

Find helicopter and passenger-drone landing sites by location or proximity across 6 endpoints, with bearer-token auth.

## Scope

Does not handle flight planning, weather, NOTAMs, slot booking, or air traffic control - use for landing-site directory lookups and proximity searches only.

## Capabilities

- Authenticate and obtain a bearer token via POST `/auth/login`
- Handle the OAuth callback for an interactive login via GET `/auth/callback`
- List landing sites in the Helipaddy directory via GET /sites
- Find the landing sites nearest to a given coordinate via GET `/sites/nearest`
- Retrieve a single site's details by id via GET `/sites/{id}`
- Inspect API usage statistics for the authenticated client via GET /usage

## Use cases

### Pilot Pre-Flight Site Lookup

A pilot's flight-planning app surfaces nearby landing sites along the planned route. The `/sites/nearest` endpoint accepts coordinates and returns the closest pads, while `/sites/{id}` provides full operational details such as contact info and surface type. The pilot does not need to maintain a landing-site database in-app.

Example prompt: Call GET `/sites/nearest`?lat=51.5&lon=-0.12 and return the five closest landing sites with their contact details

### Charter Operator Quote Tooling

A helicopter charter operator builds quotes by selecting origin and destination landing sites. The app calls /sites with region filters to populate dropdowns, then `/sites/{id}` for the chosen pad to confirm operating hours and PPR (prior permission required) status.

Example prompt: List sites with GET /sites filtered to a region, then call GET `/sites/{id}` on the selected destination to confirm PPR and contact

### Drone Operations Site Selection

A passenger-drone operator screens potential vertiport locations by checking nearby existing landing sites for clustering and accessibility. The `/sites/nearest` endpoint returns sites within a configurable radius so the operator can score candidate locations.

Example prompt: Call GET `/sites/nearest`?lat=...&lon=... for each candidate vertiport coordinate and tally the count of existing sites within 5 km

### AI Agent Aviation Concierge

An aviation concierge agent answers 'find me the nearest helipad to Battersea with PPR contact details'. Through Jentic, the agent searches by intent, loads `/sites/nearest` and `/sites/{id}`, and chains them - without ever seeing the bearer token.

Example prompt: Search Jentic for 'find nearest helipad', load GET `/sites/nearest`, and chain to GET `/sites/{id}` on the top result to return PPR contact

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/login` | Authenticate and receive a bearer token |
| GET | `/sites` | List landing sites in the directory |
| GET | `/sites/nearest` | Find the landing sites nearest to a coordinate |
| GET | `/sites/{id}` | Retrieve a single site's details |
| GET | `/usage` | Get API usage statistics for the client |

## Key resources

- **Auth** — Issue and handle bearer tokens via login and OAuth callback
- **Sites** — List, search, and retrieve landing site details, including nearest-site queries
- **Usage** — Inspect the authenticated client's API usage statistics

## Why Jentic

- **Setup:** Wiring Helipaddy by hand means posting to `/auth/login` to obtain a bearer token, then attaching the Authorization header on every directory lookup. Through Jentic you install once, import the Helipaddy Sites API from the API Directory, store the login credentials once, and your agent calls it.
- **Permission scoping:** Helipaddy puts the site id in the URL path (`/sites/{id}`) alongside read-only lookups like /sites and `/sites/nearest`, so a rule can pin your agent to reading one site or nearby sites and nothing else. The API is read-only, and you choose the operations it may call, so anything beyond those lookups is not included unless you add it.
- **Credential handling:** Your Helipaddy login credentials and the issued bearer token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find the nearest helipad' or 'look up a landing site by id', and Jentic returns the matching Helipaddy operation with its input schema, including the lat/lon and id parameters, so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Google Places API** — Google Places covers all places of interest broadly - Helipaddy is specialised to landing sites
- **Amadeus Airport & City Search** — Amadeus covers fixed-wing airports; pairs naturally with Helipaddy's helipad and vertiport directory
- **Flightradar24 API** — Flightradar24 supplies live traffic data that complements Helipaddy's static landing-site directory

## FAQ

### Why is there no official OpenAPI spec for Helipaddy Sites API?

Helipaddy documents the API on helipaddy.com/api but does not distribute a maintained OpenAPI file. Jentic generates and maintains this spec so AI agents and developers can call Helipaddy via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Helipaddy Sites API use?

Helipaddy uses bearer-token auth. POST `/auth/login` exchanges credentials for a bearer token sent on subsequent /sites and /usage requests. Through Jentic, the credentials and token live in the encrypted vault.

### Can I find the nearest helipad to a given coordinate?

Yes. GET `/sites/nearest` accepts lat and lon parameters and returns the closest landing sites, ordered by distance, so an agent can power a 'nearest helipad' lookup with a single call.

### What are the rate limits for the Helipaddy Sites API?

The OpenAPI spec does not publish hard rate limits; Helipaddy applies plan-level fair use. GET /usage returns the current period's usage, so agents can check headroom before running a bulk job.

### How do I look up a specific landing site through Jentic?

Run pip install jentic, have the agent search for 'find a helicopter landing site', load GET `/sites/{id}`, and execute it with the site id returned by /sites or `/sites/nearest.`

### Does Helipaddy include passenger-drone vertiports as well as traditional helipads?

Yes. The Helipaddy directory covers helicopter sites and passenger-drone landing sites in a single catalog, so /sites and `/sites/nearest` queries return both site types where the data exists.

### Can I limit what my agent is allowed to do with the Helipaddy Sites API?

Yes. Because you run Jentic One yourself, your own rules decide which Helipaddy operations and credentials the agent may use. The Helipaddy Sites API is read-only, so you can pin the agent to lookups such as GET /sites, GET `/sites/nearest`, and GET `/sites/{id}` by site id, and leave out anything you have not allowed. Since the site id sits in the URL path, you can scope the agent to reading one site or nearby sites and nothing else.