Skip to main content
Erebor is the SuperVaults management API. It powers vault reads, settings preparation, registries, merkle workflows, upkeep, users, pause controls, notification channels, and public vault data. Base URL: https://erebor.superform.xyz Access: These are upstream service paths. Browser requests use the session-mediated BFF; programmatic access requires an approved endpoint, identity, and scope. See Authentication.
For onchain changes, Erebor prepares calldata and the manager wallet signs the transaction. The REST request is not the state change; the signed transaction is.

Auth

Vaults and Public Discovery

Vault detail includes onchain identity, managers, fees, PPS, balances, TVL, upkeep information, activation state, and allocation data when available. Authenticated list responses may include activation; public vault responses include upkeep_info and activation when Erebor can compute them. Public discovery depends on more than deployment. Erebor only surfaces vaults with known activation when activation.is_discoverable is true. If activation is unknown because a subgraph dependency is unavailable, the vault can still be returned with activation unset rather than treated as deleted.

Vault Creation

ConfirmCreateVaultRequest can include vault_config.redeem_timelock_seconds for post-indexing settings. Distribution metadata is handled by the dashboard/listing layer after vault address resolution. Onchain creation and Superform availability are separate states.

Settings and Upkeep

Redeem timing is offchain keeper policy: the current delay applies to pending requests, including requests submitted before the setting changed. Upkeep data drives activation and discoverability in the dashboard. Read the returned threshold, shortfall, and effective activation status; exemptions can activate a vault below the funding threshold. Current upkeep responses use:

Merkle Authorization

Registry

Yield source registry entries include active/inactive state and can carry external provider metadata. Yield-source creation permits vault managers; other registry mutations have endpoint-specific maintainer policies. Upstream yield-source and oracle reads are public, which does not imply anonymous access through every BFF route.

Yield Source Whitelist

Users and Permissions

Session Keys

OMS owns additional readiness and rotation endpoints for strategy automation.

Notification Channels

Providers include Slack, webhook, and websocket channels.

Pause and Services

Analytics and Audit

Analytics endpoints live under:
Audit endpoints: