sloe/ developers
Build an integration

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 fieldExample destination fieldHandling
chartersloe_charterStable string external ID
nameinstitution_legal_namePreserve your existing account identity mapping
city, stateInstitution locationSeparate from your sales territory
websiteInstitution websiteNot a person-level identity match
assets_usdsloe_assets_usdDecimal currency, nullable
memberssloe_membersNullable membership count
net_worth_ratio_pctsloe_net_worth_ratio_pctPercent units, nullable
period, as_of_date, sourceProvenance fieldsRetain alongside financial values
profile_urlsloe_profile_urlSource-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

  1. Fetch a small filtered page and record the returned release identity.
  2. Pin every continuation page. Stop if the source changes.
  3. Validate charter uniqueness and data types in a staging table.
  4. Review unmatched or ambiguous CRM accounts.
  5. Upsert by your explicit charter-to-account mapping. Use an idempotent job key.
  6. 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.

On this page