Direct answer
Use one Nonprofit Check Plus API response to evaluate IRS-derived nonprofit status and OFAC screening, while preserving each source field separately.
Confirm the organization identity, evaluate BMF, Pub. 78 and revocation fields for the IRS side, and inspect ofac_status for the sanctions side. Then combine the policy outcomes your application needs.
Recommended verification flow
- Normalize the EIN.
- Call the Nonprofit Check Plus API.
- Confirm
einandorganization_name. - Review BMF status and classification.
- Review Pub. 78 presence and contribution data.
- Review revocation and reinstatement history.
- Review
irs_bmf_pub78_conflictwhen relevant. - Read
ofac_status. - Check source freshness.
- Combine application-level policy outcomes without losing source detail.
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 |
|---|---|---|
bmf_status |
Supplies BMF presence. | Apply IRS-status rules. |
pub78_verified / organization_types |
Supplies Pub. 78 contribution context. | Apply deductibility or contribution rules. |
| Revocation fields | Supplies revocation and reinstatement history. | Apply current-status policy. |
irs_bmf_pub78_conflict |
Supplies documented foundation-classification conflict context. | Route conflicting classification according to policy. |
ofac_status |
Supplies organization-level OFAC status. | Apply sanctions-screening policy separately. |
| Source dates | Supplies freshness context. | Route stale or conflicting source combinations appropriately. |
Example decision logic
A combined workflow might:
- confirm identity;
- calculate an IRS policy outcome from the required IRS fields;
- calculate an OFAC policy outcome from
ofac_status; - preserve all source fields;
- stop or review when either policy requires it; and
- keep the reason for each decision traceable to its source.
Important: Combining the workflow does not mean merging the underlying IRS and OFAC meanings.
Why use a consolidated nonprofit verification API?
One API call can support multiple compliance checks while keeping source context intact.
One normalized response
Receive IRS verification and OFAC screening in one response.
Separate source signals
Preserve tax, deductibility, revocation and sanctions dimensions independently.
Reusable compliance rules
Apply the same combined workflow across donations, grants, onboarding and fintech.
Developer-friendly automation
Build one decision layer without maintaining separate external data integrations.
Frequently asked questions
Which field contains the OFAC result?
Use ofac_status.
Which fields should drive IRS verification?
Use the BMF, Pub. 78, foundation and revocation fields required by your specific workflow.
Should I create one universal verified field?
The supplied API does not define one universal verified field. Keep source outcomes traceable.
Can the same logic be used in bulk?
Yes. The bulk response returns the same organization-level field model for each item.
Related Pactman artifacts
- How to Screen a Nonprofit Against the OFAC SDN List
- How to Add OFAC Screening to a Nonprofit Verification Workflow
- How to Verify Multiple Nonprofits in Bulk Using EINs
Next step
Keep IRS and OFAC source fields separate, compute explicit policy outcomes for each, and combine only the workflow decision your application needs.
Ready to combine IRS and OFAC checks?
Use Pactman Nonprofit Check Plus API to evaluate IRS and OFAC signals in one application workflow.