sloe/ developers
Understand the data

Periods, sources and releases

Make “current” precise and keep historical reads reproducible.

A quarterly period such as 2026-Q3 describes a reporting interval. An as-of date and a source capture time describe different things. Keep all returned context rather than deriving one date from another.

Do not infer the quarter from the product homepage

The web app, licensed API, individual original reports and downloadable bulk packages can have different release lifecycles. Read the response or manifest for the exact data you are consuming. Retained institutions can have an older period than the main response cohort.

The published REST contract is API version 1.3.0, verified November 4, 2026. Default financial reads include the available Q3 individual reports. The Q3 cohort is not a complete final-quarter census; the complete final-bulk default remains Q2. Release status.

Release identities

release_id pins a supported financial product release. platform_release_id pins a supported application/platform context. Supply only identifiers actually returned by the endpoint and described in its contract. A 409 means your pinned view cannot be served consistently; restart rather than mixing releases.

The published API uses a separate current_release_id for the current-report layer. For default current-list continuations, preserve both the returned historical release.id and current_release.id as release_id and current_release_id. An integration that receives current_release metadata should preserve both the historical product identity and the current identity; never relabel a historical product release as a Q3 release.

Explicit history

Where supported, pass period and release_id from your chosen response. Use a supported explicit view for historical reads. A period filter is not a promise that every requested quarter is available. History endpoints can omit unavailable periods rather than inventing observations.

Annual HMDA, branch research and vendor records retain their own dates. Proposed merger notices and reported approvals are separate stages; an approval is not proof that a merger has completed.

On this page