/easa/type_certificates/search

POST /api/easa/type_certificates/search

Price: 10 credits

Search EASA type certificate data sheets (TCDS) by keyword, product type and year range. Each data sheet carries its code, title, issue number, the TCDS PDF and the TCDS for Noise PDF when published.

How to use it

The technical content of a data sheet is only in its PDF. Pass `id` or `url` to easa/type_certificates for the product type, TC holder and annex documents.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of type certificate data sheets to return (min: 1)
• keyword string nullable — Words from the code or title (examples: "A380")
• product_type string nullable — Product type (one of: "aircraft", "airship", "airship_cs30_cs31ha", "balloon", "engine", "propeller", "rotorcraft")
• year_from integer nullable — Earliest year (examples: 2020; min: 1900; max: 2100)
• year_to integer nullable — Latest year (examples: 2022; min: 1900; max: 2100)

Response

• @type string (default: "EasaTypeCertificate")
• id string required
• name string nullable
• issue integer nullable
• product_type string nullable
• manufacturers array (default: [])
• tcds_document object nullable
  • @type string (default: "EasaDocument")
  • url string required
  • file_name string nullable
  • file_type string nullable
  • size_bytes integer nullable
• noise_document object nullable
  • @type string (default: "EasaDocument")
  • url string required
  • file_name string nullable
  • file_type string nullable
  • size_bytes integer nullable
• documents array (default: [])
  • @type string (default: "EasaDocument")
  • url string required
  • file_name string nullable
  • file_type string nullable
  • size_bytes integer nullable
• noise_url string nullable
• node_id string nullable
• alias 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 — The entity was not found, or a precondition failed 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.