Authentication¶
Aurastream uses two layers of authentication:
- Aurastream API key — authenticates you against the Aurastream service
- Data source credentials — your own credentials for third-party data providers (when required)
Aurastream API Key¶
Every request must include your Aurastream API key in the x-api-key header:
You can find your API key in the Aurastream dashboard under API Keys.
Keep your API key secret
Never commit your API key to version control or share it publicly. Use environment variables or a secrets manager.
Data Source Credentials¶
Some data sources require your own API credentials to access their data. These are passed in the credentials field of the request body — they are not stored on Aurastream servers.
response = requests.post(URL, headers=headers, json={
"tickerlist": ["EUR_USD"],
"start": "2025-01-01",
"end": "2025-06-01",
"interval": "1h",
"source": "oanda",
"credentials": {
"id": "YOUR_OANDA_ACCOUNT_ID",
"token": "YOUR_OANDA_TOKEN",
"environment": "practice"
}
})
Credentials are never stored
Aurastream forwards your credentials directly to the upstream data source in real time. They are not saved, logged, or cached.
Which sources need credentials?¶
| Source | Credentials Required | Notes |
|---|---|---|
| Oanda | Yes | Account ID + API token |
| Alpaca | Yes | API key + secret |
| Polygon | Yes | API key |
| FRED | Yes | API key |
| Finnhub | Yes | API key |
| Binance | No | Public market data |
| Bybit | No | Public market data |
| Kraken | No | Public market data |
| Yahoo Finance | No | Public data |
See the Credentials guide for the exact format each source expects.