POST /api/iso/standards
Price: 5 credits
Get one ISO standard by its catalogue number. Returns the public catalogue record: reference, title, scope abstract, publication status and harmonised stage code, edition and edition year, publication date, page count, list price in Swiss francs with the per-language and per-format purchase options, the owning technical committee, the ICS classification codes, the standards this one replaces or is replaced by, its amendments and corrigenda, the dated stage history of the project, and the UN Sustainable Development Goals ISO maps it to.
The input is ISO's internal catalogue number — the digits in www.iso.org/standard/62085.html — not the reference a document is cited by: ISO 9001:2015 is catalogue number 62085, and passing 9001 resolves a different, unrelated standard. Get the number from /iso/standards/search, which returns it as `id`. Every edition of a reference has its own catalogue number, so `related_standards` is how you move between them: it names the previous and superseding editions with their own numbers, and `stage` plus `stage_title` say where the current one sits in ISO's lifecycle, with 90.93 meaning confirmed and 95.99 withdrawn. `amendments` lists the separately purchasable Amd and Cor documents, which are not folded into the base text. The standard's own text is paywalled and is not returned; `abstract` is the public scope statement and is missing on a minority of records.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)standard string required — ISO catalogue number of the deliverable, or a www.iso.org/standard/ URL containing it (examples: "62085", "75736", "https://www.iso.org/standard/62085.html"; minLength: 1)@type string (default: "IsoStandard")id string requiredreference string nullablestandard_title string nullableabstract string nullableurl string nullablestatus string nullablestage string nullablestage_title string nullableedition string nullableedition_year integer nullablepublication_date string nullablepage_count integer nullableprice object nullable@type string (default: "IsoPrice")amount number nullablecurrency string nullableavailability string nullablelanguages array (default: [])purchase_options array (default: [])@type string (default: "IsoLanguageFormat")language string nullablelanguage_name string nullablepurchase_format string nullableformat_code string nullableamount number nullablecommittee object nullable@type string (default: "IsoCommitteeReference")id string nullablereference string nullablecommittee_title string nullableurl string nullableics array (default: [])@type string (default: "IsoIcsReference")code string nullablecode_title string nullableurl string nullablerelated_standards array (default: [])@type string (default: "IsoRelatedStandard")id string nullablereference string nullablerelation string nullablestage string nullableurl string nullableamendments array (default: [])@type string (default: "IsoAmendment")id string nullablereference string nullablelabel string nullableamendment_title string nullableedition string nullableurl string nullablestage_history array (default: [])@type string (default: "IsoStageEvent")code string nullablestage_title string nullabledate string nullablesustainable_development_goals array (default: [])@type string (default: "IsoSustainableDevelopmentGoal")number integer nullablegoal_title string nullable422 — The input is not a catalogue number or a www.iso.org/standard/ URL 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 ISO standard carries that catalogue 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.