Service, updates and support
What Data Access delivers, how updates reach you and where to get help.
What your subscription delivers
Data Access provides the documented read-only API and licensed downloadable files for your internal systems. You can create and revoke your API keys in your Sloe account. The manifest lists the files and periods available to your key. Start with a verified download.
Your organization operates its own import or CRM integration. The subscription includes the documented data delivery; customer-specific integration development and redistribution arrangements require their own agreement.
When the data changes
Financial filings describe quarters. We publish updates after source collection and validation; an upstream publication date is not a guaranteed Sloe delivery date. Available individual reports can appear before a complete quarterly bulk package. We label that coverage explicitly rather than presenting a partial cohort as a complete quarter.
Branches, vendor evidence, mortgage filings and regulatory events have their own source dates. Read the returned period, source context and manifest instead of assigning one refresh date to every dataset. Understand periods and releases.
Check the manifest before an import. Save its release identities and checksums with your imported data so you can tell whether a later run uses a different edition.
Report a data problem
Email info@thecreditunionwire.com with the institution's charter, field name, reporting period, source/release identity and the source you believe differs. For a failed API request, include its HTTP status, approximate time and trace_id.
We check the source and affected outputs before publishing a correction. A corrected file has a new checksum or delivery revision. Restart an interrupted import when a release conflict is returned; keep the original manifest if you need to reproduce an earlier result. See the release history.
Access problems and service interruptions
Use the same support email for authentication, downloads and billing questions. Do not send API keys, passwords, signed download links or full sensitive request logs. An invoice reference and the account email are enough to begin a billing inquiry.
Support follows the existing Terms of Service. We make reasonable efforts to give advance notice of planned downtime when possible. Availability and resolution times are not guaranteed by the standard subscription. Any separately agreed service level belongs in your written customer agreement.
Keep your import compatible
Read the release history before changing your integration. Accept documented additional fields, preserve source identities and validate the fields you use. If a change affects an existing integration, contact support with the version and endpoint so we can review it with you.
Redeem a short-lived data-feed broker token GET
Normally reached through the Location header returned by /api/data-feed when a file is requested (curl -L redeems it in the same request). The token expires in 120 seconds by default, is single-use, and is bound to the customer of the requesting key: the same Authorization: Bearer key used for /api/data-feed is required here too. The broker rechecks the originating key, its bound customer, package release and any bound delivery revision, and refuses a second redemption of the same token. Current private packages redirect to a freshly signed storage URL; historical legacy packages retain their configured delivery.
Errors, limits and retries
Handle failures explicitly and keep imports recoverable.