/easa/airworthiness_directives

POST /api/easa/airworthiness_directives

Price: 1 credit

Get an airworthiness directive or other safety publication from the EASA Safety Publications Tool by number: issuing authority, issue and effective dates, EASA approval number, ATA chapter, approval holders with aircraft types and models, revision, correction and supersedure notes, related publications, remarks and attachment files.

How to use it

Covers EASA directives and the foreign authority directives the tool republishes, keyed by their own number such as US-2026-17-08. A revision has its own number with an R suffix, so pass the exact number from easa/airworthiness_directives/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• number string required — Publication number as issued, revision suffix included, or its ad.easa.europa.eu URL (examples: "2026-0144R1", "US-2026-17-08", "https://ad.easa.europa.eu/ad/26-105"; minLength: 1)

Response

• @type string (default: "EasaDirective")
• id string required
• subject string nullable
• issued_by string nullable
• issue_date string nullable
• effective_date string nullable
• approval_number string nullable
• ata_chapter string nullable
• approval_holders array (default: [])
  • @type string (default: "EasaApprovalHolder")
  • name string required
  • aircraft_types array (default: [])
    • @type string (default: "EasaAircraftType")
    • name string required
    • models array (default: [])
• revision string nullable
• correction string nullable
• supersedure string nullable
• related_publications string nullable
• remarks string nullable
• attachments array (default: [])
  • @type string (default: "EasaAttachment")
  • url string required
  • file_name string nullable
  • file_type string nullable
  • size string nullable
• url string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No publication with this number Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.