Kindsight Integrations API teaching reference · v20240515 · unofficial
Every endpoint, parameter and response here is extracted programmatically from the Postman collection — nothing is retyped. Quotes are verbatim; values are labelled Tier A · source-verbatim or Tier B · authored illustration. How this was built →

Learn the Kindsight (iWave) Integrations API — with the receipts

A wealth-screening and prospect-research API for nonprofit CRMs. This site teaches it from primary sources: every fact is extracted from the public Postman collection or quoted from the public Onboarding Guide, and every analytical claim is re-verified by code you can read.

14
endpoints
28
saved response examples
563
schema fields mapped
3
deprecated endpoints

Two ways to screen a constituent

Single profile — synchronous

POST /profile creates a profile and generates wealth scores in one call. Retrieve later by your CRM's own constituent ID — you never store a Kindsight key.

Start with Create a Profile →

Bulk screening project — asynchronous

Up to 1,000,000 records per batch through a 6-step, server-enforced lifecycle: create → load → process → poll → retrieve → reconcile errors.

Run the interactive lifecycle →

Lessons

Lesson 1 · Authentication — what the docs say, and what the file does

OAuth 2.0 with two grant types, a dedicated auth host — and a collection that promises tooling it doesn't contain.

Lesson 2 · The bulk screening lifecycle — a 6-step state machine

Create, load, process, poll, retrieve, reconcile — with the server enforcing order. Interactive simulator included.

Lesson 3 · Deprecation done well — scores became part of profiles

Three endpoints are deprecated for a reason you can see in the data model itself.

Lesson 4 · Reading the error surface

Two envelope shapes, a status-type flip, and what each 4xx teaches about the server's state machine.

Lesson 5 · Reading generated fixtures critically

The examples in this collection are correct as shape and wrong as meaning. Learning to tell the difference is a transferable skill.

Findings — where the documentation and the file disagree

Real integrations fail on the gaps, so the gaps are first-class content here. Each finding is machine-verified at every ingest.

CodeSeverityFinding
G1 high The collection's Quick Start describes auth machinery the file does not contain
G2 medium Saved example data is schema-shaped but semantically incoherent
G3 medium CSV upload is documented, but the CSV schema is absent
G4 low scoreConfiguration affinity codes are an undocumented vocabulary
G5 medium Five endpoints return arrays; only one is paginated
G6 medium Two incompatible error envelopes — with a type flip inside one endpoint

Endpoint reference

Credits — Screening credit balance

Score Request — Deprecated — superseded by Profile