/propublica_nonprofit/organizations

POST /api/propublica_nonprofit/organizations

Price: 1 credit

Profile of a US tax-exempt organization by EIN: registration and IRS classification details, headline financial figures, and its whole Form 990 filing history with the extracted line items.

How to use it

Pass an EIN in either form — 941340523 or 94-1340523 both resolve. No separate call is needed for the filing history: `filings` carries one entry per electronically filed return with the extracted IRS line items under `line_items` (raw IRS 990 variable names, and the set differs by form type), while `filings_without_data` lists older returns the source holds only as a scanned PDF. Every `pdf_url` points at ProPublica's own download page, which is behind a bot check and answers 403 to a programmatic fetch — treat it as a link to hand a human, not as a file you can retrieve. On `filings` the source states only the form family, so `form_family` reads 990 for a 990, a 990-R and a 990-O alike, while the exact form name is given only on `filings_without_data`. If you hold a name rather than an EIN, resolve it through propublica_nonprofit/organizations/search first.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• ein string required — Employer Identification Number of the organization, with or without the hyphen (examples: "941340523", "94-1340523"; minLength: 1)

Response

• @type string (default: "PropublicaNonprofitOrganization")
• ein string required
• name string required
• url string required
• sort_name string nullable
• care_of_name string nullable
• address string nullable
• city string nullable
• state string nullable
• zipcode string nullable
• ntee_code string nullable
• subsection_code integer nullable
• classification_codes string nullable
• activity_codes string nullable
• affiliation_code integer nullable
• foundation_code integer nullable
• organization_code integer nullable
• deductibility_code integer nullable
• exempt_organization_status_code integer nullable
• exemption_number integer nullable
• filing_requirement_code integer nullable
• pf_filing_requirement_code integer nullable
• asset_code integer nullable
• income_code integer nullable
• accounting_period integer nullable
• asset_amount number nullable
• income_amount number nullable
• revenue_amount number nullable
• ruling_date string nullable
• tax_period_date string nullable
• latest_object_id string nullable
• irs_data_source string nullable
• created_at integer nullable
• updated_at integer nullable
• filings array (default: [])
  • @type string (default: "PropublicaNonprofitFiling")
  • tax_period string required
  • tax_year integer nullable
  • form_family string nullable
  • form_type_code integer nullable
  • pdf_url string nullable
  • updated_at integer nullable
  • total_revenue number nullable
  • total_functional_expenses number nullable
  • total_assets_end number nullable
  • total_liabilities_end number nullable
  • officer_compensation_share number nullable
  • line_items object (default: {})
    • * union
• filings_without_data array (default: [])
  • @type string (default: "PropublicaNonprofitFilingStub")
  • tax_period string required
  • tax_year integer nullable
  • form_type string nullable
  • form_type_code integer nullable
  • pdf_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 organization is registered under that EIN 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.