Your first verified download
Create a key, download a Parquet file and verify it before importing.
1. Create your API key
Sign in to Sloe Data with the email used for your purchase and complete any password-setup prompt. Open Account, choose Generate Key, give it a recognizable label and copy the full key when it is shown. It is shown only once.
Store it in a password manager or your server's secret store. You can revoke an exposed or unused key from the same account page. If a paid subscription is not recognized, contact support with your account email and invoice reference; do not purchase a second subscription to work around an access error.
These examples assume your terminal already has SLOE_API_KEY set securely. It is a local variable name, not a required Sloe SDK setting. Never put a working key in a URL, screenshot, chat or shared script.
2. Choose the period and format
Discover available packages with GET /api/data-feed. Its available_periods lists the published periods and formats. The default complete bulk package currently remains Q2 2026. Q3 2026 contains 4,154 available financial reports and is explicitly not a complete final-quarter census.
This walkthrough selects the Q3 financial cohort deliberately:
curl --fail-with-body --silent --show-error \
'https://sloedata.com/api/data-feed?period=2026-Q3' \
-H "Authorization: Bearer $SLOE_API_KEY" \
--output manifest.jsonRead data.complete_quarter, data.coverage, data.current_release and data.files before importing. For a complete historical package, choose an available final quarter instead.
3. Download the listed Parquet file
curl --fail-with-body --silent --show-error --location \
'https://sloedata.com/api/data-feed?period=2026-Q3&file=institutions.parquet' \
-H "Authorization: Bearer $SLOE_API_KEY" \
--output institutions.parquetThe key authorizes the Sloe request and its same-origin download broker. The final private-storage URL is signed and temporary. Do not add --location-trusted, which can forward your key to another host. Request a fresh download link if a temporary link expires.
4. Verify the file
This Python example uses only the standard library. It checks the downloaded length and SHA-256 against the manifest you saved:
import hashlib
import json
from pathlib import Path
manifest = json.loads(Path('manifest.json').read_text())
if manifest.get('ok') is not True:
raise RuntimeError('Manifest request did not succeed')
expected = next(
item for item in manifest['data']['files']
if item['path'] == 'institutions.parquet'
)
file = Path('institutions.parquet')
digest = hashlib.sha256()
with file.open('rb') as stream:
for chunk in iter(lambda: stream.read(1024 * 1024), b''):
digest.update(chunk)
if file.stat().st_size != expected['bytes']:
raise RuntimeError('File length differs from the manifest')
if digest.hexdigest() != expected['sha256']:
raise RuntimeError('File checksum differs from the manifest; do not import')
print('Verified:', file.name)5. Import and keep the source context
Load into a staging table first. Keep charter as a string; preserve decimal types and nulls. The Q3 file includes period, source_release_id and source_manifest_sha256 alongside the financial fields. Save the original manifest with the import.
For a CRM, map charter to a dedicated external-ID field and review ambiguous matches before writing. Keep financial periods with their values and decide how your sync handles nulls. Follow the CRM field mapping and import sequence. This walkthrough prepares a verified input file; it does not send records to a CRM.