Chart List

The terminal chart list of an airport: approach, departure, arrival, taxi and reference charts with their index numbers, revision dates and document IDs. The IDs returned here are what you use to download a chart — see Chart Documents.

Required roles: AIS Jeppesen Charts API, AIS Charts Data via Cloud — Roles
Base endpoint: https://jepp-api.ibosoft.net.tr:2087/charts
Attribution: show ibonav.aero wherever this data is displayed
Last updated: 17 OCT 2026

A chart is identified by two numbers: docId (the document) and docBinaryId (the printable file). Both are stable — the same chart at the same revision always keeps the same IDs, and a new revision of a chart is published under a new pair of IDs. An older docBinaryId keeps working and serves the current image of that chart.

Endpoints

Endpoint Description
GET /charts/{icao} All terminal charts of one airport

Parameters

Name In Type Required Description
icao path string ✔ Airport ICAO code, case-insensitive (ltac = LTAC)
coverages query (repeatable) string[] — Accepted for backward compatibility; does not change the result. If given but empty → 400

Response

Field Type Description
charts Chart[] The chart list, in index-number order
total int Number of charts

Chart

Field Type Description Example
chartType string Chart category (see below) "APP"
description string Chart title "ILS Y OR LOC Y RWY 03L"
indexNum string Index number "11-1"
icaoIdentifier string Airport ICAO code "LTAC"
docId string Document ID "800000062"
docBinaryId int File ID — used by GET /pdf/{doc_binary_id} 900000062
revDate int | null Revision date, Unix epoch milliseconds at UTC midnight 1786060800000
effDate null Effective date is not published; always null null

chartType values

Value Charts
APP Instrument approach charts
SID Departure procedures
STAR Arrival procedures
TAXI Airport, parking and taxi charts (index numbers starting with 10-9)
REF Reference charts — airport briefing, general information

Any other category is passed through as given; an empty one becomes REF.

Example

{
  "charts": [
    {
      "chartType": "REF",
      "description": "AIRPORT BRIEFING (GEN)",
      "indexNum": "10-1P",
      "icaoIdentifier": "LTAC",
      "docId": "800000001",
      "docBinaryId": 900000001,
      "revDate": 1782432000000,
      "effDate": null
    },
    {
      "chartType": "APP",
      "description": "ILS Y OR LOC Y RWY 03L",
      "indexNum": "11-1",
      "icaoIdentifier": "LTAC",
      "docId": "800000062",
      "docBinaryId": 900000062,
      "revDate": 1786060800000,
      "effDate": null
    }
  ],
  "total": 90
}

Errors

Errors are returned as {"detail": "<message>"}.

Code Meaning
200 with {"charts": [], "total": 0} Unknown airport — not an error
400 coverages was given but contains no usable code
500 Upstream failure (Failed to fetch charts: <code>)

Notes

  • A chart can only be downloaded after the chart list of its airport has been requested at least once; listing is what makes the IDs resolvable. Clients that store docBinaryId values long-term should refresh the list before downloading.
  • The list is not cached; every call returns the current state. A call takes about 0.3–1.2 s.
  • indexNum is the stable key for "the same chart over time" in a user interface; docBinaryId changes with every revision.

Examples

# All charts of LTAC
curl 'https://jepp-api.ibosoft.net.tr:2087/charts/LTAC'

# Approach charts only (jq)
curl -s 'https://jepp-api.ibosoft.net.tr:2087/charts/LTAC' | jq '.charts[] | select(.chartType == "APP")'