/charitycommission/charities

POST /api/charitycommission/charities

Price: 20 credits

Profile of a charity on the register of England and Wales by its registered number: what it does, who it helps, where it operates, its latest income and expenditure with the reported breakdowns, staff, trustee and volunteer numbers, employee benefit bands, and its contact details.

How to use it

Pass the registered charity number, including the suffix of a linked sub-charity such as 1089464-1. The figures here cover the latest financial year only, named in `financial_year_end`; for the five-year series call charitycommission/charities/financial_history. The breakdown amounts in `income_breakdown` and `expenditure_breakdown` are the rounded figures the register displays, so read `amount_text` when the rounding matters and take `total_income` and `total_expenditure` as the exact ones. Trustees, governance, annual returns and linked charities each have their own endpoint.

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: "CharitycommissionCharity")
• charity_number string required
• organisation_number string required
• name string required
• url string required
• reporting_status string nullable
• activities string nullable
• financial_year_end string nullable
• total_income number nullable
• total_expenditure number nullable
• investment_gains_text string nullable
• government_contract_income number nullable
• government_contract_count integer nullable
• government_grant_income number nullable
• government_grant_count integer nullable
• income_breakdown array (default: [])
  • @type string (default: "CharitycommissionMoneyBreakdown")
  • label string required
  • amount number nullable
  • amount_text string nullable
• expenditure_breakdown array (default: [])
  • @type string (default: "CharitycommissionMoneyBreakdown")
  • label string required
  • amount number nullable
  • amount_text string nullable
• employee_count integer nullable
• trustee_count integer nullable
• volunteer_count integer nullable
• employee_benefit_bands array (default: [])
  • @type string (default: "CharitycommissionEmployeeBenefitBandCount")
  • band string required
  • employee_count integer nullable
• fundraising_note string nullable
• trading_note string nullable
• trustee_payments_note string nullable
• main_way_of_working string nullable
• purposes array (default: [])
• beneficiaries array (default: [])
• activity_types array (default: [])
• areas_of_operation array (default: [])
• address array (default: [])
• phone string nullable
• email string nullable
• web_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 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.