The retail intelligence API built from real investor behavior
Rallies turns investor questions, connected portfolios, AI-managed fund activity, and SEC filings into structured API signals. The platform tracks more than $500M in connected portfolio value, contains a six-figure retail conversation corpus, and has indexed more than a million filing passages for semantic retrieval. Across the product, Rallies processed 25B+ model tokens last year.
This is not another price, news, or social feed. It is a behavioral intelligence layer: what retail investors are asking before they trade, how connected portfolios are positioned after decisions are made, how AI funds are allocating capital, and what company filings say underneath the move.
Use it when a dashboard, quant pipeline, analyst workflow, RIA product, or enterprise data product needs normalized retail and AI behavior signals instead of raw consumer records.
Why Rallies
Most retail datasets are lagging: trade prints, end-of-day flow, public social posts, or noisy message boards. Rallies adds the missing layer: high-intent investor questions before trades happen, portfolio-confirmed behavior after capital moves, and filing context to explain the fundamentals behind the signal.
What you can build
The API is useful anywhere retail behavior needs to become a programmatic signal.
Prerequisites
To use the Rallies API, you need:
X-Rallies-API-Key header.https://api.rallies.ai/v1 for all v1 endpoints.Content-Type: application/json when the endpoint accepts a JSON body.Making your first request
Start with a simple retail-intent query. This asks what question themes are showing up for a ticker over a recent window.
curl "https://api.rallies.ai/v1/retail/intent/questions?ticker=NVDA&days=7&limit=5" \
-H "X-Rallies-API-Key: $RALLIES_API_KEY"The response is already aggregated. You should not expect raw questions or raw user counts.
{
"themes": [
{
"rank": 1,
"label": "Earnings Setup",
"sentiment": "mixed",
"question_share_pct": 18.44,
"related_tickers": [
{ "ticker": "AMD", "question_share_pct": 22.5 }
]
}
]
}Available APIs
The API is split by product area and workflow. Each endpoint has its own reference page with parameters and examples.
Authentication
All requests must include an API key header.
X-Rallies-API-Key unless your integration has a custom auth agreement.Request format
GET endpoints use query parameters. POST endpoints accept JSON bodies and are used when requests need richer text input, multi-value filters, or streaming options.
/retail/intent/questions?ticker=NVDA&days=7./retail/intent/ask and /filings/ask.limit. Endpoint pages show the exact accepted parameters.Response format
Responses are compact JSON objects shaped around the resource you asked for. The API does not echo backend filters, expose raw user counts, or return implementation metadata.
themes, topics, flows, funds, results, or companies.snapshot_at, latest_trade_at,executed_at, or filing.date.question_share_pct, conversation_share_pct, ownership_share_pct, or net_flow_pct.Streaming
Ask-style endpoints support streaming when the request includes stream: true. Streaming is useful for chat products, internal analyst tools, and long filing-grounded answers.
stream is false unless explicitly enabled.Privacy and aggregation
Rallies API products expose aggregated intelligence, not individual consumer records. Retail intent endpoints summarize question themes and topics. Portfolio endpoints return aggregated holdings, flows, rotation, and options activity. AI fund endpoints expose managed strategy outputs, not private user accounts.
Errors
The API uses standard HTTP status codes. When a request fails, the response body is JSON and includes an error message when available.
Versioning
All current endpoints live under /v1. New versions will use a new version prefix instead of silently changing the behavior of existing routes.