Quickstart
Get your API key and make your first request in under five minutes.
Make your first request
REST endpoints for filings, funds, and events.
Choose a workflow
Guides for NAV, disclosures, filings, dividends, and board changes.
Use the SDK
Python client with webhook verification, event parsing, and API helpers.
Receive webhooks
Signed push delivery for market events.
1. Get an API key
Sign in at portal.rangler.co and create an organization. Then generate a sandbox API key.
The key is shown once. Copy it to your secret manager or .env file immediately.
2. Pick your integration path
Start with webhooks for production event delivery. Use event feeds for initial reads, backfills, and reconciliation.
See Webhooks and Event Feeds for the trade-offs, and SDKs if you want a typed client instead of raw HTTP.
2a. Pick a workflow package
Start with a workflow, not a raw endpoint list. Fund Monitoring covers NAV, disclosures, and fund updates. Issuer Monitoring covers filings, dividends, and board changes.
3. Make your first request
curl -s https://sandbox-api.rangler.co/v1/filings?limit=5 \
-H "X-API-Key: atl_test_your_key_here" | python3 -m json.toolcurl -s https://sandbox-api.rangler.co/v1/funds?limit=5 \
-H "X-API-Key: atl_test_your_key_here" | python3 -m json.toolcurl -s "https://sandbox-api.rangler.co/v1/events?limit=10" \
-H "X-API-Key: atl_test_your_key_here" | python3 -m json.toolResponses are JSON. Errors follow Errors.
4. Explore the data
Try:
| Endpoint | What it returns |
|---|---|
GET /v1/companies | NGX-listed companies with sector and ticker |
GET /v1/companies/{id}/filings | Filings for a specific company |
GET /v1/funds/{id} | Fund detail with latest_snapshot (most recent NAV) and latest_holdings_snapshot (most recent disclosure with holdings) |
GET /v1/funds/{id}/snapshots | Historical fund snapshots with month-over-month and year-over-year deltas |
GET /v1/events?type=dividend.declared | Filter the event feed by type |
See the API Reference for the full endpoint list.
5. Add Atlas SDKs
Use ranglerpy for webhook verification, typed event parsing, idempotency helpers, and API reads. See SDKs.
6. Receive events via webhook
For webhooks:
Register a webhook endpoint
Create the endpoint in the portal and point it at the receiver URL you want to validate.
Send a test ping
Validate transport and signing before you subscribe to live traffic.
Create an event subscription
Filter by event type, company, or fund.
Receive signed deliveries
Atlas sends matching events with retries and HMAC signatures.
See Webhooks for delivery behavior and signature verification, and Events for the event taxonomy and payload format.
6a. Test in sandbox before you go live
Use Sandbox Testing for synthetic events, webhook pings, subscription-scoped generation, and delivery logs.
7. Go live
For production:
Generate a live key
Create an atl_live_ key and keep it separate from sandbox.
Switch to the live base URL
Use https://api.rangler.co/v1.
Review webhook targets and subscriptions
Webhook endpoints and subscriptions are managed at the organization level. Confirm the receiver URL and rules before enabling live traffic.
Handle rate limits cleanly
Back off on 429 responses. See Errors.
API keys and data-plane traffic are isolated by environment. Webhook configuration is managed at the organization level. See Environments.