How to Verify 50 Nonprofit EINs in a Single API Request

Direct answer

Use the Pactman nonprofitcheckbulk endpoint and submit an array of up to 50 normalized EIN strings.

The UPDATED-v2 template explicitly states that a bulk-EIN request can contain at most 50 EINs. Each organization returned in the bulk data array uses the same current 43 organization-level fields as the single-EIN response, so your application can reuse the same verification rules for every item.

Recommended verification flow

Normalize every EIN. Remove spaces and dashes before building the array.
Remove duplicates when your workflow requires it.
Split larger jobs into groups of no more than 50 EINs.
Send the EIN array to the bulk endpoint.
Confirm the top-level response succeeded.
Iterate through data.
Match each returned ein to the requested EIN.
Apply your existing IRS, revocation and OFAC rules to each organization.
Review nonprofit_check_count for returned-organization usage.
Use timeTaken for operational monitoring when useful.

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 EIN array	Carries multiple nonprofit identifiers in one request.	Keep each request at or below the documented 50-EIN maximum.
`data`	The bulk response contains an array of organization results.	Iterate and evaluate one organization result at a time.
`ein`	Identifies each organization result.	Map each response object back to the requested EIN.
Current 43 organization fields	The supplied single and bulk samples use the same organization-level schema.	Reuse the same per-nonprofit verification code.
`nonprofit_check_count`	The mapping defines this as the number of organizations returned during the billing cycle.	Track usage from the returned value.
`timeTaken`	Top-level timing value in the supplied responses.	Use for performance observation when needed.

Example decision logic

A bulk worker might:

chunk 137 EINs into requests of 50, 50 and 37;
submit each chunk to the bulk endpoint;
iterate through the returned data array;
map each item by ein;
apply the same BMF, Pub. 78, revocation and OFAC rules used for single checks; and
preserve nonprofit_check_count and timeTaken as top-level operational values.

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

Important: The 50-EIN maximum is a per-request limit. Bulk transport does not change the meaning of any organization-level field.

Why use a consolidated nonprofit verification API?

High-volume platforms often need to verify many organizations without issuing one network request per EIN.

Pactman's bulk endpoint lets the application process up to 50 EINs while preserving the same per-organization schema.

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 organization.

Reusable compliance rules

Use the same single-EIN rules for each bulk item.

Developer-friendly automation

Chunk larger jobs predictably and process returned organizations by EIN.

Frequently asked questions

Can I send exactly 50 EINs in one bulk request?

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

What should I do with 51 or more EINs?

Split them into multiple requests, each containing no more than 50 EINs.

Does the bulk endpoint return a different organization schema?

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

What does `nonprofit_check_count` represent?

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

Next step

Normalize the EIN list, batch it into groups of up to 50, submit each batch, and reuse your existing per-organization verification logic on the returned data items.

Ready to verify 50 EINs at a time?

Use Pactman Nonprofit Check Plus bulk API to process up to 50 nonprofit EINs per request with one consistent response model.

Get an API Key →