How do I authenticate API requests?
Send your API key in the Authorization header as a Bearer token. Contact us at [email protected] to get a key.
Every live dataset sits behind one REST API: clean endpoints, JSON responses, and a single API key. No SDK required.
All six live datasets mount at the root of one base URL: /insider-transactions, /institutions/holdings, /proposed-sales, /funds/list, /supply-chain/{ticker}, and /ipos. There is no versioned path maze to memorize.
Auth is one header, Authorization: Bearer YOUR_API_KEY, and every response is JSON. Conventions stay consistent across endpoints: uppercase tickers, ISO dates, _gte and _lte suffixes for range filters, and a limit parameter for page size.
The whole API is described by a public OpenAPI 3.1 spec. Generate a client in your language, build a mock server for tests, or import the spec into Postman. The spec and the API ship together, so they don't drift.
Dataset endpoints mount at the API root: /insider-transactions, /ipos, and the rest. Integrate once, then add datasets by adding paths.
The full API is described by a public spec, so you can generate clients, mock servers, and tests in any language.
Every response is normalized JSON with consistent field names across datasets. Parse once, reuse everywhere.
Per-endpoint limits are exposed in X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers. Your retry logic works off facts, not guesses.
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://ryxel.io/api/insider-transactions?ticker=AAPL"One Bearer key, JSON responses, predictable conventions. Most integrations start returning data in an afternoon.
Point your generator at the OpenAPI spec and get a typed client in Python, TypeScript, Go, or anything else with a generator.
Requests plus pandas is a complete stack. Pull a slice, plot it, iterate.
Structured JSON and a machine-readable spec make the API callable by LLM agents and workflow tools without custom parsing.
Send your API key in the Authorization header as a Bearer token. Contact us at [email protected] to get a key.
All endpoints return JSON. Schemas are documented in the OpenAPI 3.1 spec and the dataset docs.
At the API root: /insider-transactions, /ipos, and so on. There is no /api/ prefix to add.
Limits are per endpoint and depend on your plan. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers, so client code can back off before hitting a 429.
Yes, OpenAPI 3.1 and public. Use it to generate clients, mocks, and tests, or to import the API into tools like Postman.
Tell us what you're building and which datasets you need — we'll set you up with an account, an API key, and access to the data.