/propublica_nonprofit/people/search

POST /api/propublica_nonprofit/people/search

Price: 5 credits

Search officers, directors, trustees and key employees named on US nonprofit Form 990 filings. Returns the person, the role and organization they are named under, the fiscal year, and the base, related and other compensation reported for them.

How to use it

One result is one person-on-one-filing, so the same person appears once per organization and per fiscal year they were reported in — deduplicate on `organization_ein` and `fiscal_year` if you want a single row per person. `min_organization_compensation` bounds what the organization reported, not what this person was paid. Use `organization_ein` from a result to pull the organization's own profile from propublica_nonprofit/organizations.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Words matched against the person's name as it appears on the filing (examples: "gates", "maria rodriguez"; minLength: 1)
• years array — Fiscal years of the filing the person is named in (default: []; examples: [2023,2022])
• states array — Two-letter US state or territory codes of the organization's address (default: []; examples: ["WA","CA"])
• min_organization_compensation string nullable — Keep only people whose organization reported total compensation of at least this many USD (one of: "10000", "25000", "50000", "100000", "150000", "200000", "250000", "300000", "400000", "500000", "1000000", "2500000")
• sort string — Order of the results (default: "best"; one of: "best", "name", "-name", "year", "-year", "org_comp", "-org_comp")
• count integer required — Max number of people to return (min: 1; max: 5000)

Response

• @type string (default: "PropublicaNonprofitPerson")
• name string required
• role string nullable
• organization_name string nullable
• organization_sub_name string nullable
• organization_ein string nullable
• organization_url string nullable
• city string nullable
• state string nullable
• fiscal_year integer nullable
• base_compensation number nullable
• related_compensation number nullable
• other_compensation number nullable
• filing_object_id string nullable
• filing_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.