/charitycommission/charities/governance

POST /api/charitycommission/charities/governance

Price: 10 credits

How a charity on the register of England and Wales is constituted and governed: legal form, company number, other names it works under, other regulators it answers to, the policies it reports having, its registration history, and the governing document with the charitable objects and area of benefit.

How to use it

`registration_history` is where a merger shows up: an entry naming another charity carries its number in `related_charity_number`, which you can feed straight back into these endpoints. `policies` lists what the charity told the register it has in place, so absence means it was not reported rather than that no policy exists. `charitable_objects` is the legal purpose text from the governing document, which is what to read when the question is what the charity may lawfully fund.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• charity_number string required — Registered charity number as it appears on the register, including the suffix of a linked sub-charity (examples: "1089464", "1089464-1"; minLength: 1)

Response

• @type string (default: "CharitycommissionGovernance")
• charity_number string required
• organisation_number string required
• organisation_type string nullable
• company_number string nullable
• gift_aid string nullable
• land_and_property string nullable
• other_names array (default: [])
• other_regulators array (default: [])
• policies array (default: [])
• registration_history array (default: [])
  • @type string (default: "CharitycommissionRegistrationEvent")
  • date string required
  • event string nullable
  • related_charity_number string nullable
• governing_document string nullable
• charitable_objects string nullable
• area_of_benefit 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 charity is registered under that 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.