How to Automate Nonprofit Due Diligence for a Grantmaking Platform

Q: Which fields are most important for revocation screening?

Use `revocation_code`, `revocation_date` and `reinstatement_date`.

Q: Can OFAC screening be included in the same workflow?

Yes. Use `ofac_status` as a separate sanctions-screening signal.

Direct answer

Automate grantmaking due diligence by calling Pactman Nonprofit Check Plus API when a grantee enters or updates its EIN, then apply your grant policy to the returned source fields.

Confirm organization identity, evaluate BMF and Pub. 78 signals relevant to the grant program, review revocation and reinstatement history, and inspect ofac_status. Keep those signals separate and let the grantmaking application decide whether to continue, review or stop.

Recommended verification flow

Normalize the grantee EIN.
Call the Nonprofit Check Plus API.
Confirm ein and organization_name.
Review bmf_status, bmf_subsection and subsection_description.
Review pub78_verified and contribution fields when the grant policy requires them.
Review foundation classification fields when foundation type matters.
Check revocation_code, revocation_date and reinstatement_date.
Review ofac_status.
Check source freshness and irs_bmf_pub78_conflict when relevant.
Apply an explicit continue, review or stop policy and retain the source signals needed for audit.

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
`ein` / `organization_name`	Identifies the intended grantee.	Continue only when the returned organization matches the applicant.
`bmf_status` / BMF classification	Supplies IRS organization and subsection context.	Apply the grant program's tax-status rules.
`pub78_verified` / `organization_types`	Supplies Pub. 78 and contribution-classification context.	Use when the grant program requires contribution or charity eligibility signals.
Foundation fields	Provides public-charity/private-foundation context.	Apply foundation-type policy without deriving it solely from BMF subsection.
Revocation fields	Provides revocation and reinstatement history.	Route historical or unresolved revocation according to grant policy.
`ofac_status`	Provides organization-level OFAC screening status.	Apply sanctions review separately from IRS eligibility.
Freshness and conflict fields	Source dates and `irs_bmf_pub78_conflict` help identify stale or conflicting records.	Route ambiguous cases to review instead of silently overwriting sources.

Example decision logic

A grantmaking platform might:

validate the grantee identity by EIN;
require the BMF/Pub. 78 signals relevant to the grant program;
check foundation classification;
review revocation and reinstatement history;
screen ofac_status;
route source conflicts or stale records to compliance review; and
save the returned source fields with the grant decision.

For portfolio reviews, the same policy can run through the bulk endpoint in batches of up to 50 EINs.

Important: The current API does not expose a field named grant_eligible. Eligibility is an application policy outcome built from the source fields your grant program requires.

Why use a consolidated nonprofit verification API?

Grantmaking due diligence often spans IRS status, contribution eligibility, revocation history, foundation classification and sanctions screening.

Pactman returns those signals in one organization model and supports bulk review for larger grantee portfolios.

One normalized response

Evaluate multiple nonprofit due-diligence dimensions from one API response.

Separate source signals

Keep tax status, deductibility, revocation and OFAC evidence traceable.

Reusable compliance rules

Apply the same grantee policy during intake, approval and recurring review.

Developer-friendly automation

Trigger workflow actions and bulk portfolio checks from explicit returned fields.

Frequently asked questions

Does Pactman return a `grant_eligible` field?

No. The current supplied schema returns source signals; the grantmaking application applies its own eligibility policy.

Which fields are most important for revocation screening?

Use revocation_code, revocation_date and reinstatement_date.

Can OFAC screening be included in the same workflow?

Yes. Use ofac_status as a separate sanctions-screening signal.

Can I review many existing grantees at once?

Yes. Use the bulk endpoint for batches of up to 50 EINs and apply the same per-organization policy.

Next step

Map the grant program's eligibility and review rules to the returned Pactman fields, then run the same policy during intake and recurring grantee reviews.

Ready to automate grantee due diligence?

Use Pactman Nonprofit Check Plus API to bring IRS, revocation and OFAC signals into the grantmaking decision workflow.

Get an API Key →