Nonprofit Data Export API: How to Download IRS 990 Data at Scale
If you are looking for a nonprofit data export API to download records into your own application, warehouse, or CRM, the hard part is not finding a CSV button. The hard part is choosing a data source that gives you the records you need without an enterprise contract, per-record charges, or an IRS ingestion pipeline you have to maintain.
There are several ways to approach the problem. Some tools are built for broad nonprofit research and enrichment. Others expose raw IRS files and leave the engineering to you. 501see is built for the developer who wants structured public 990-derived data that can move from an initial export into an API-powered product.
Nonprofit data export API options
The important differences are not just the number of records in a database. Look at how the data is delivered, how exports are priced, and whether the tool supports the workflow after the initial download.
501see
501see provides filtered asynchronous CSV exports for organizations, grants, and officers, along with a read API and webhooks. The subscription model has no per-record or per-export fees. It is the best fit for developers building on public 990-derived data who want to move from an initial export into a live product.
Cause IQ
Cause IQ combines nonprofit research, enrichment, API, and bulk export tools. Its public pricing lists Core exports at $0.50 per record. Pro is listed at $4,488 per year, with each export capped at 3,000 records. See the Cause IQ pricing page.
Cause IQ may be the right choice for teams that need a broader prospecting and enrichment suite. For a developer who wants to load a large public-data set into their own system, per-record pricing can become expensive quickly.
Candid
Candid offers nonprofit APIs and data products with broader profile and compliance coverage. Its public API pricing lists Essentials starting at $4,800 for 40 fields and Premier starting at $9,900. See the Candid API pricing page.
Candid can make sense for organizations buying a sales-led data product. It is a different proposition from a self-serve workflow for developers who mainly need public 990-derived records.
IRS bulk files
The IRS bulk data downloads provide public filings in raw XML. There is no vendor subscription, but your team owns the downloading, parsing, normalization, retry, and maintenance work.
IRS files are a good foundation if building and operating the pipeline is part of your project. If it is not, the engineering cost can outweigh the apparent savings.
Prices and limits can change, so verify the linked vendor pages before making a purchasing decision. The broader point is stable: a developer who wants to export public nonprofit data should not have to pay for a large research suite or pay again for every row.
Where 501see is the better fit
501see is the better option when your goal is to put nonprofit data into a product you control:
- Predictable export economics. Export charges do not grow with every row, and there are no per-export fees.
- A developer-first workflow. Create an asynchronous export, download the CSV, then use the read API for targeted records and application features.
- The data you actually need. Export organizations, grants, or officers using the same filters as the corresponding search endpoints.
- A path beyond the initial download. Webhooks can support change notifications when a one-time backfill becomes a live integration.
Cause IQ and Candid may be the right choice if you need their broader research, enrichment, compliance, or fundraising features. If you primarily need public 990-derived records in your own system, 501see gives you a simpler and more affordable path.
When an export is the right tool
An export makes sense when you need to move a meaningful set of records into a system you control:
- Seed a nonprofit directory or marketplace
- Load organization data into Postgres, BigQuery, Snowflake, or another warehouse
- Build an internal research dataset
- Pull a filtered group of grant or officer records for analysis
- Create a one-time snapshot for a migration or backfill
If you only need the current data for one organization, the nonprofit 990 API is the simpler path. An export becomes valuable when repeating individual API requests would turn your application into a data-ingestion project.
What you can export
Developer Pro supports asynchronous CSV exports for three resource types:
- Organizations for building a nonprofit dataset or directory
- Grants for analyzing funding relationships at scale
- Officers for research and compensation-related workflows
Each export accepts filters from the corresponding list or search endpoint. That lets you narrow the dataset before it is generated instead of downloading everything and filtering it yourself afterward. You can also provide an email address for a completion notification.
How an export works
An export is a job, not a long-running request that your application has to keep open:
- Choose the resource type and filters.
- Create the export job through the API.
- Check the job status while the file is prepared.
- Download the CSV when the job is complete.
The job-based workflow is useful for scheduled backfills and operational tools because the initial request can finish while the larger dataset is being prepared. Your application can store the job ID, check it later, and handle the completed file when it is ready.
Export first, then build the live workflow
An export and a read API solve different parts of the same integration:
- Use an export for the initial backfill or a large filtered dataset.
- Use the read API when your application needs a specific organization, filing, grant, or officer record.
- Add change notifications when the workflow needs to stay current over time.
This is the practical path from a blank database to a working nonprofit data product. You can start with the dataset you need, then add more targeted API access as the application becomes more interactive.
Developer Free, Basic, and Pro
The developer plans map to these different jobs:
- Developer Free covers verification-oriented organization and latest-filing lookups.
- Developer Basic provides the broader read API for applications that need ongoing access to nonprofit data.
- Developer Pro adds asynchronous exports for initial backfills, filtered datasets, and warehouse loads.
If you are evaluating the data or building a live lookup, start with the read API. If you need to move a substantial dataset into your own system, create a developer account and use the export workflow available with Developer Pro.