Donor API: the static resource guide

What is available

DonorAPI.com publishes complete HTML charity profiles, paginated browse pages, a field dictionary, collection insights, an XML sitemap, and an RSS feed. All charity data is present in the delivered pages. No account, database connection, source-file download, or browser-side data fetch is required to read a profile.

Resource addresses

A profile address combines a readable organization name and EIN digits. For example, 1000 Friends of Oregon is published at:

Published HTML resourceContent type: text/html

GET /charities/1000-friends-of-oregon-930642086/

A complete HTML page containing the mission,
classification, historical scores, financial fields,
and all 23 original source values.

The charity directory and its category, location, size, score-band, and alphabetical routes link to that same canonical page. Their pagination is implemented as real directory pages, not query parameters that require a backend.

What is not an active service

There is no authenticated JSON endpoint, API-key issuance, live ratings feed, write API, donor account, donation processor, tax-status verification call, or CRM synchronization service on this website. Illustrative record panels explain structure; they do not advertise an endpoint that can be called.

A field model you can understand

The source has 23 fields. Its EIN is a text identifier; scores are historical numbers on a 100-point scale; expense shares are fractions; dollar amounts are in US dollars; and classification labels retain the source vocabulary. The dictionary records the definitions and display transformations.

Each profile’s “Inspect all 23 original source fields” section is rendered in the HTML using a native expandable section. Readable formatting is separate from the original values. JSON-LD supplies page and organization identity metadata; it is not a replacement for the complete visible record or a separate data API.

Discovery files

The XML sitemap enumerates canonical indexable pages. The RSS feed includes substantive pages and the full text of the ten Donor Fieldnotes articles. Blog publication dates are kept separate from the historical collection period. Directory entries do not invent individual rating dates.

Planning a future integration

Start by defining identity, provenance, units, missing-value handling, update policy, and reuse rights. Then determine whether the actual application needs static reference pages, a licensed data feed, current verification, or a private operational backend. These are different requirements and should not be blended into one unlabeled “API” promise.

The supplied metadata lists the data license as unknown. Review the reuse notes before building additional distribution formats. For an external service, consult Charity Navigator’s API and business resources and verify the provider’s applicable access and usage terms.