Rillet

At a Glance

Difficulty

⚡MODERATEAPI Key Authentication + API Access Enabled per Organisation by Rillet

Authentication

API KeyAPI key presented as a Bearer token in the Authorization header — not OAuth. Keys are scoped to a single Rillet organisation.

Webhooks

No webhooks

Partnership Required

No

Apideck Credentials

Not available(Not available — each consumer connects with their own Rillet organisation API key; there is no app to register.)

Costs

No API-specific fee. Rillet itself is a paid platform and does not publish pricing.

Sandbox Availability

Available(A separate sandbox environment at sandbox.api.rillet.com with its own API keys, arranged through your Rillet team.)

Account Type Required

A Rillet account. Any plan works; there is no edition gate on API access.

Consumer Access Level

Admin access to Organization Settings, which is where API keys are created.

Rate Limits

60 requests per rolling one-minute window; requests above it return HTTP 429.

Responsibility matrix

Environments

Sandbox

Purpose: development and testing against sandbox.api.rillet.com. Credentials: a sandbox API key created in that environment's Organization Settings. Access is arranged through your Rillet team, the same route as production API access — there is no self-service sandbox signup.

Production

Purpose: live financial data on api.rillet.com, using a production API key created at https://app.rillet.io/settings/api-access.

Critical

Sandbox and production API keys CANNOT be used against each other. The environment is selected when the connection is created in Vault, so a key and an environment that disagree simply fail to authenticate.