Enrich CRM accounts
Match by charter, retain provenance and keep the write step in your integration.
Sloe returns institution data. Your integration maps the fields and writes to the CRM using that CRM's credentials and permissions. There is no automatic Salesforce or HubSpot sync implied by an API response.
Match the institution first
Use the NCUA charter number as the Sloe-side key. Keep it as a string. Store it in a dedicated external-ID field and explicitly map it to the CRM's account ID. A shared name, website domain or address is a lead for matching, not proof that two accounts are the same institution.
Search with the institution list, review ambiguous matches, then use detail for the selected charter. Keep branches as child locations rather than creating duplicate institution accounts.
Suggested field mapping
The following source fields are from an institution-list result (data.results[]). Detail responses use nested groups; consult their separate schema.
| Sloe list field | Example destination field | Handling |
|---|---|---|
charter | sloe_charter | Stable string external ID |
name | institution_legal_name | Preserve your existing account identity mapping |
city, state | Institution location | Separate from your sales territory |
website | Institution website | Not a person-level identity match |
assets_usd | sloe_assets_usd | Decimal currency, nullable |
members | sloe_members | Nullable membership count |
net_worth_ratio_pct | sloe_net_worth_ratio_pct | Percent units, nullable |
period, as_of_date, source | Provenance fields | Retain alongside financial values |
profile_url | sloe_profile_url | Source-product link |
Keep the enclosing data.release metadata and any additional release identities returned by the endpoint in your sync log. Research relationships and branches retain their own source dates and identifiers.
A reliable sync sequence
- Fetch a small filtered page and record the returned release identity.
- Pin every continuation page. Stop if the source changes.
- Validate charter uniqueness and data types in a staging table.
- Review unmatched or ambiguous CRM accounts.
- Upsert by your explicit charter-to-account mapping. Use an idempotent job key.
- Record the source release, import time and destination write result.
A missing result is not an instruction to delete a CRM account. A null value is not a reported zero. Decide explicitly whether a missing value clears a previously stored field or retains it with its old period; never leave an old value labeled with a new quarter.
What to expect
This is institution enrichment, not a complete executive prospecting directory. The licensed API contract does not promise personal email addresses, direct dials or LinkedIn profiles. Reviewed vendor relationships are evidence-bounded records, not proof of every installed product or contract renewal date.