How to Verify a Nonprofit Whose Name Has Changed

Recommended verification flow

1. Normalize the EIN.
2. Send the EIN to the Nonprofit Check Plus API.
3. Anchor on ein.
4. Review organization_name.
5. Review organization_name_aka when populated.
6. Compare bmf_organization_name.
7. Compare pub78_organization_name.
8. Review source-specific EINs. Check bmf_ein and pub78_ein.
9. Check freshness.
10. Treat differing names as identity context, not a documented change date.

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

Example decision logic

A name-matching layer might:

• require the intended EIN;
• normalize case and punctuation for comparison without overwriting source text;
• compare organization_name, organization_name_aka, bmf_organization_name and pub78_organization_name;
• confirm source-specific EINs; and
• retain source dates.

The supplied single sample for EIN "996589560" shows organization_name: "ABORJAILY BANNISH FOUNDATION", bmf_organization_name: "ABORJAILY BANNISH FOUNDATION" and pub78_organization_name: "Aborjaily Bannish Foundation". These presentation differences are identity context, not proof of a historical legal name change.

Important: The supplied response does not provide a field that states when a name changed.

Why use a consolidated nonprofit verification API?

Name differences are easier to resolve when the EIN, alternate name and source-specific IRS names appear together.

Pactman Nonprofit Check Plus preserves those values in one response.

One normalized response

Compare multiple supported name representations around one EIN.

Separate source signals

Preserve BMF and Pub. 78 names instead of replacing them with one normalized string.

Reusable compliance rules

Apply consistent name matching across onboarding, grants and donations.

Developer-friendly automation

Reduce false mismatches caused by case, punctuation or alternate-name differences.

Frequently asked questions

Which field contains an alternate nonprofit name?

Use organization_name_aka when it is populated.

Can the current API tell me the date the nonprofit changed its name?

No. The current supplied schema does not include a dedicated name-change date field.

Should I verify the EIN even when the names look similar?

Yes. Use the EIN and source-specific EIN fields to anchor identity.

Are BMF and Pub. 78 names always formatted exactly the same?

The supplied samples show that presentation can differ.

Related Pactman artifacts

• How to Verify a Nonprofit That Uses a DBA or Doing-Business-As Name
• How to Verify a Nonprofit When Its IRS Address Is Different From Its Current Address
• How to Determine Which IRS Record Is Newer When Nonprofit Data Conflicts

Next step

Anchor identity on the EIN, compare the supported name fields, preserve source-specific names, and avoid inventing a name-change timeline.