/iso/committees

POST /api/iso/committees

Price: 20 credits

List ISO technical committees, subcommittees and joint committees. Returns the reference, the English and French titles, the scope statement, the standing, the creation date, the secretariat body, the parent and child committees, and the national standards bodies taking part as participating or observing members together with the committee and organization liaisons. Filters by reference or id, by parent committee, by standing, to top-level committees only, or by a substring of the reference, title and scope.

How to use it

References are ISO's own spelling — 'ISO/TC 176', 'ISO/TC 176/SC 3', 'ISO/IEC JTC 1' — and the numeric form is the committee id that /iso/standards returns in `committee.id`, so either resolves. Walk the tree with `top_level_only` for the roots and `parent` for the level below; a working group under a subcommittee is a committee here too. `participating_members` are the national bodies that vote, `observing_members` follow the work without voting, and the acronyms are the member-body codes such as ANSI, BSI and DIN. Committees this endpoint reports as Suspended have stopped meeting but keep their published standards in force, so do not read the standing as a statement about the standards.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• committees array nullable — Committee references or ISO committee ids to return (examples: ["ISO/TC 176"], ["ISO/TC 176/SC 3","ISO/IEC JTC 1"], ["53934"])
• parent string nullable — Return the subcommittees and working groups directly under this committee (examples: "ISO/TC 176", "53882"; minLength: 1)
• statuses array nullable — Committee standing (one of: "Active", "Suspended")
• top_level_only boolean — Keep only committees that sit directly under ISO rather than under another committee (default: false)
• query string nullable — Case-insensitive substring matched against the reference, the English title and the scope (examples: "quality", "nanotechnologies"; minLength: 1)
• count integer required — Max number of results to return (min: 1; max: 900)

Response

• @type string (default: "IsoCommittee")
• id integer required
• reference string nullable
• committee_title string nullable
• title_fr string nullable
• scope string nullable
• scope_fr string nullable
• status string nullable
• creation_date string nullable
• url string nullable
• secretariat object nullable
  • @type string (default: "IsoMemberBody")
  • id integer nullable
  • acronym string nullable
• parent_id integer nullable
• children_ids array (default: [])
• participating_member_count integer nullable
• observing_member_count integer nullable
• participating_members array (default: [])
  • @type string (default: "IsoMemberBody")
  • id integer nullable
  • acronym string nullable
• observing_members array (default: [])
  • @type string (default: "IsoMemberBody")
  • id integer nullable
  • acronym string nullable
• committee_liaisons array (default: [])
  • @type string (default: "IsoCommitteeLiaison")
  • id integer nullable
  • reference string nullable
• organization_liaisons array (default: [])
  • @type string (default: "IsoOrganizationLiaison")
  • id integer nullable
  • acronym 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 committee matched the filters 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.