The OJC Fund API integration & DAF OpenData services

Account & identity module

Wraps the OJC donor login flow, including session token refresh and profile management. Endpoints expose mailing address, phone numbers, email contacts, and bank account references — the same fields users edit inside the app — so external CRMs (Salesforce NPSP, HubSpot, Bloomerang) can keep contact data in sync with the donor's source of truth.

Grant recommendation module

Programmatic submission of grant recommendations to any of the 8,000+ OJC-supported charities, identified by EIN or internal organization ID. Includes idempotency keys, recommendation memo fields, and status tracking from submitted → approved → paid, mirroring the in-app "recommend funds to your favorite charities" workflow.

Check-book & monthly book module

Endpoints to order check booklets, query monthly book replenishment status, and pull issuance history. Useful for donors who use OJC's tracked, hand-to-hand check-book product as part of their giving cadence and need that activity reflected in personal-finance tools.

Charity directory search

A search wrapper over the OJC-vetted charity directory: lookup by EIN, name, NTEE category, or geography. Returns OJC-supported flag, recent grant volume, and recommended payment rail. Supports building "smart" donor-side search experiences and grant-eligibility pre-checks.

Statement & tax-receipt module

Date-ranged statement APIs producing IRS-ready PDF receipts and structured JSON line items for each contribution and grant. Pairs cleanly with year-end tax workflows, accountant hand-off packages, and audit logs needed under proposed IRS Section 4966 reporting expectations.

Reconciliation & webhooks

Outbound webhook events for grant approval, check clearance, contribution settlement, and balance change. Each event carries a stable event_id and occurred_at timestamp so downstream ledgers (QuickBooks, Sage Intacct, NetSuite) can reconcile DAF activity without polling.

1. Year-end tax-receipt pipeline

Context: A high-net-worth donor needs consolidated annual giving reports across multiple DAFs and family-office accounts. Data: contribution history (asset type, FMV, date) plus grant recommendations and disbursements. OpenData mapping: mirror the OJC /statement read endpoint into the family-office data warehouse, normalize against IRS Form 8283 fields, and emit a single tax-year PDF + structured JSON ledger ready for the donor's CPA.

2. CRM contact-data refresh

Context: A nonprofit treats OJC-recommended grants as a primary inbound channel and wants accurate donor-side contact info. Data: donor profile, mailing address, email. OpenData mapping: with explicit donor authorization, push profile changes from OJC into Salesforce NPSP via webhooks; the nonprofit sees address corrections and email updates the same day the donor edits them in-app, eliminating returned-mail and stale-list waste.

3. Grant-disbursement reconciliation

Context: Recipient charity finance teams must reconcile incoming OJC checks with donor advisories so acknowledgments are accurate. Data: grant recommendation events plus check clearance webhooks. OpenData mapping: match an inbound bank deposit to the corresponding OJC grant recommendation_id, then auto-generate a thank-you letter referencing the originating donor (where consent allows) instead of an anonymous DAF block.

4. Advisor dashboard for DAF accounts

Context: Wealth advisors managing client philanthropic plans (OJC notably collaborates with brokerage firms including Charles Schwab and Equinum Wealth Management) need a unified view across multiple DAF sponsors. Data: balance, investment allocation, cumulative giving, grant cadence. OpenData mapping: normalize OJC account data alongside Fidelity Charitable, Schwab Charitable, and Daffy data into a single OpenFinance-style schema (account → transactions → grants).

5. Compliance & audit trail

Context: Following the November 2023 IRS proposed regulations on Section 4966 taxable distributions, sponsoring organizations and donor-advisors face broader recordkeeping expectations. Data: recommendation submission timestamp, advisor identity, fund-manager approvals, final disbursement record. OpenData mapping: ship every recommendation lifecycle event (submitted, reviewed, approved, paid) into an immutable WORM log with hashed payloads, reducing audit prep time and supporting joint-and-several-liability evidence trails.

Deliverables checklist

• OpenAPI 3.1 specification for donor account, grant, and statement endpoints
• Protocol & auth flow report (token exchange, refresh chain, MFA hooks)
• Runnable source code in Python (FastAPI) and Node.js (Express / TypeScript)
• Webhook receiver template with HMAC verification
• Postman collection plus integration test suite
• Compliance notes on IRS Section 4966 proposed regulations and donor-data retention
• Source code delivery from $300 — pay after delivery upon satisfaction
• Pay-per-call hosted API option — usage-based billing, no upfront commitment

API example: donor login (pseudocode)

POST /api/v1/ojc/auth/login
Content-Type: application/json

{
  "username": "donor@example.org",
  "password": "********",
  "device_id": "sdk-fingerprint-9f2c"
}

Response 200:
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_8a91...",
  "expires_in": 1800,
  "donor_id": "OJC-D-103942",
  "mfa_required": false
}

API example: statement export

GET /api/v1/ojc/statement
Authorization: Bearer <ACCESS_TOKEN>

?from_date=2025-01-01
&to_date=2025-12-31
&format=json

Response 200:
{
  "donor_id": "OJC-D-103942",
  "period": "2025",
  "contributions": [
    {"date":"2025-03-04","asset":"AAPL","fmv_usd":12500.00,"shares":62},
    {"date":"2025-09-12","asset":"USD","fmv_usd":5000.00}
  ],
  "grants": [
    {"date":"2025-04-10","charity_ein":"13-1234567",
     "amount_usd":2500.00,"recommendation_id":"rec_a91"}
  ],
  "balance_end_usd": 18342.55
}

API example: grant recommendation webhook

POST https://your-app.example.com/webhooks/ojc
X-OJC-Signature: t=1714200000,v1=hmac_sha256(...)
Content-Type: application/json

{
  "event_id": "evt_2K1f...",
  "occurred_at": "2026-04-15T14:22:09Z",
  "type": "grant.paid",
  "data": {
    "recommendation_id": "rec_a91",
    "charity_ein": "13-1234567",
    "amount_usd": 2500.00,
    "check_number": "OJC-CK-008842",
    "cleared_at": "2026-04-15T13:55:01Z"
  }
}

Regulatory alignment

Donor-advised funds in the United States operate under Internal Revenue Code Section 4966, with proposed regulations (issued November 2023, refined through 2024) defining taxable distributions, donor-advisor scope, and excise taxes on sponsoring organizations and fund managers. Our integrations preserve full advisory and approval lineage so that any recommendation can be reconstructed for IRS examination.

For donors aged 70½ and older, note that under SECURE Act 2.0, DAFs remain ineligible recipients for Qualified Charitable Distributions (QCDs) — our reporting layer flags QCD-style transfers so they are not misclassified.

Data handling

Personal donor data — addresses, phone numbers, bank references — is treated as restricted PII. We apply tokenization for bank account references, encrypt payloads in transit (TLS 1.3) and at rest, and follow data-minimization defaults so downstream systems receive only the fields they have a documented purpose to consume. NDAs and explicit donor-authorization records are part of every engagement.

Engagement workflow

1. Scope confirmation: integration scenarios and API needs (login, statements, grants, webhooks).
2. Protocol analysis and API design (2–5 business days, complexity-dependent).
3. Build, internal validation, and compliance review (3–8 business days).
4. Docs, samples, Postman collection, and test cases (1–2 business days).
5. Typical first delivery: 5–15 business days; third-party approvals or sandbox provisioning may extend timelines.

FAQ

What do you need from me?

How long does delivery take?

How do you handle compliance?

Can you integrate OJC alongside other DAFs?