How to Verify Multiple Nonprofits in Bulk Using EINs

Direct answer

Use the Pactman nonprofitcheckbulk endpoint and send an array of EIN strings in the request body.

The UPDATED-v2 template states that a bulk request can contain at most 50 EINs. The supplied bulk sample returns a top-level data array, with each organization using the same current 43 organization-level fields found in the single-EIN response.

Recommended verification flow

Normalize every EIN.
Remove duplicates when your application policy requires it.
Limit each request to at most 50 EINs.
Send the EIN array to the bulk endpoint.
Confirm the top-level response succeeded.
Iterate through the data array.
Match each returned ein to the requested identifier.
Apply the same IRS and OFAC rules used for single-EIN results.
Review nonprofit_check_count.
Record timeTaken when useful for operational monitoring.

Example request(s)

curl --request GET \
  --url https://entities.pactman.org/api/entities/nonprofitcheck/v1/us/ein/YOUR_EIN \
  --header 'Authorization: Bearer YOUR_API_KEY'

Implementation note: The endpoint name above reflects the Pactman single-EIN Nonprofit Check endpoint used in Pactman's Production/Customer Environment.

curl --request POST \
  --url https://entities.pactman.org/api/entities/nonprofitcheckbulk/v1/us/eins \
  --header 'accept: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '[
    "YOUR_EIN_1",
    "YOUR_EIN_2",
    "YOUR_EIN_3",
    "YOUR_EIN_4",
    "YOUR_EIN_5"
  ]'

Implementation note: The endpoint name above reflects the Pactman bulk-EIN Nonprofit Check endpoint used in Pactman's Production/Customer Environment. You can have at most 50 EINs in a bulk-EIN Nonprofit Check endpoint request.

What your application should evaluate

Signal	Why it matters	Typical application decision
Bulk request array	Carries multiple EIN strings in one request.	Keep each request within the 50-EIN limit.
`data`	The bulk sample returns an array of organization results.	Iterate one organization at a time.
`ein`	Identifies each returned organization result.	Map the result back to the requested EIN.
Current 43 organization fields	The bulk and single examples use the same organization-level field set.	Reuse the same verification logic for each item.
`nonprofit_check_count`	The mapping defines this as the total number of organizations returned during the billing cycle.	Track usage according to the returned value.
`timeTaken`	Top-level response timing value in the supplied sample.	Use for operational observation if your application needs it.

Example decision logic

A bulk-verification worker might:

split a larger job into batches of no more than 50 EINs;
submit each array;
iterate over data;
map each result by ein;
apply the same per-organization IRS and OFAC rules used in single checks; and
retain the top-level usage and timing values as needed.

The supplied bulk sample returns five organization records and nonprofit_check_count: 5.

Important: Bulk processing changes the transport shape, not the meaning of the organization-level verification fields.

Why use a consolidated nonprofit verification API?

Bulk verification reduces request overhead for batch onboarding, grants, donations and compliance review.

One normalized response

Receive multiple organization results in one top-level response.

Separate source signals

Preserve BMF, Pub. 78, revocation and OFAC fields for every returned organization.

Reusable compliance rules

Apply the same single-EIN policy logic across each bulk item.

Developer-friendly automation

Process up to 50 EINs per request using one consistent result model.

Frequently asked questions

How many EINs can I send in one bulk request?

The UPDATED-v2 template states that the bulk endpoint accepts at most 50 EINs per request.

Does the bulk response use different organization fields?

The supplied single and bulk samples use the same current 43 organization-level fields.

What is `nonprofit_check_count`?

The supplied mapping defines it as the total number of organizations returned during the billing cycle, resetting at the start of each billing cycle.

Can I reuse my single-EIN verification rules?

Yes. Apply the same per-organization field logic to each item in the bulk data array.

Next step

Batch normalized EINs in groups of up to 50, iterate over the returned data array, and reuse your existing per-organization verification rules.

Ready to verify EINs in bulk?

Use Pactman Nonprofit Check Plus bulk API to evaluate multiple nonprofit EINs in one request.

Get an API Key →