Business · head-to-head
Charity Search vs Google Analytics
CharityAPI (rebranded from OrgHunter) looks up US nonprofits by EIN across basic profile, financial, geolocation, and NTEE-classification datasets, sourced from IRS filings and pitched at donation platforms and vetting tools. Its real backend at `data.orghunter.com` trades a query-string `user_key` for JSON responses and rejects unauthenticated calls with a 403, and offers free development-phase API keys with production usage gated behind paid or affiliate-only plans.
The Google Analytics 4 Data API (`analyticsdata.googleapis.com/v1beta`) lets applications pull custom reports of metrics, dimensions, and audience segments out of a GA4 property, complementing a separate Admin API used to manage properties, streams, and access. It requires a Google OAuth 2.0 bearer token, confirmed live via a `WWW-Authenticate: Bearer realm="https://accounts.google.com/"` challenge on an unauthenticated `runReport` call, and the same request repeated with an Origin header echoed `access-control-allow-origin` back, resolving CORS support from unknown to yes. The core Data API is free to call within Google's standard quotas, with Google Analytics 360 offered as a paid enterprise tier for higher limits and additional features.
| Charity Search | Google Analytics | |
|---|---|---|
| Authentication | API Key | OAuth |
| Pricing | freemium | freemium |
| Formats | JSON | JSON |
| CORS | no | yes |
| HTTPS | Yes | Yes |
Google Analytics supports CORS, while Charity Search doesn't — pick Google Analytics for direct browser calls.