> For the complete documentation index, see [llms.txt](https://docs.syntetika.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.syntetika.io/for-integrators/using-our-api.md).

# Using our API

The Syntetika API is a public REST interface for reading vault data: the vaults, their prices and capacity, NAV history, cycle dates, and each account's positions and pending requests.&#x20;

Use it to list the vaults in your product, show a participant what they hold and what is waiting to settle, and chart performance. The API never submits transactions; deposits and redemptions are made on-chain (see **Deposits and Redemptions** below).

## What You Can Build

* **A vault list.** GET /general/vaults returns every vault with TVL, share price, net APY and managers; GET /vault/:vault adds the next strike, attestation window and settlement dates. net\_apy and max\_drawdown are null until a vault has two NAV strikes.
* **A participant's position.** GET /ember/positions/:account returns what an address holds in every vault with realized and unrealized yield; GET /ember/deposits/:account and GET /ember/withdrawals/:account return the requests still waiting to settle, each with its status and settlement window.
* **Performance charts.** GET /performance/:vault returns share price, TVL, APY and NAVC return series; GET /navc/history returns the attested NAV for each strike once its rate is on-chain.
* **Statements and transparency.** GET /navc/statement serves the NAVC investor statement PDF for a month, and the /transparency routes return the data behind the Transparency dashboard.

#### Showing a pending deposit

For a participant’s pending deposits, `GET /ember/deposits/:account` returns each request with a `status`, a settlement window and a countdown. Read the status as: Awaiting Settlement before the window opens, Pending inside it, Delayed once the window has passed without settlement. Show the window, `settle_date` to `settle_date_max`, not a single date: the NAV finalizes typically within five business days of the strike, up to fifteen.

Every route, parameter and response field is documented on the [API Reference](https://docs.syntetika.io/for-integrators/api-reference.md) page.

## Deposits and Redemptions

Participants can deposit and redeem in the Syntetika app, on Ember's page for the vault, or by calling the contracts directly. A deposit is a request submitted to the vault's deposit contract; the vault token mints when the strike NAV is published, not on arrival. A redemption is requested on-chain; shares are queued, dealt at the next strike NAV and paid once settlement runs. Deposits can be canceled until the cutoff and redemptions until they are paid.

Every deposit is screened at entry against blockchain-analytics risk scores. A deposit from a flagged address is rejected and the address is blocked, so your interface should handle a rejected deposit.

The vault and deposit contracts are Ember Protocol's. Ember's documentation is at [learn.ember.so](https://learn.ember.so); its API Docs page links the @ember-finance/sdk package and the OpenAPI specification of its vaults API. If a participant holds a token other than the vault's asset, GET /enso/zap returns one ready-to-sign transaction that swaps into the deposit asset and submits the deposit request; send any preTransactions it returns before tx.

## Contracts

The vault contract is also the vault token: hBTC and oneUSD are balances on it. The deposit contract receives deposit requests. Verify addresses against this page and never copy them from explorer lists or token searches, where lookalike addresses exist. Never transfer the deposit asset directly to either contract; a direct transfer registers no deposit request.

<table><thead><tr><th width="92.15625">Vault</th><th width="96.96484375">Network</th><th width="84.81640625">Deposit Asset</th><th>Vault ID</th><th>Vault Contract</th><th>Deposit Contract</th></tr></thead><tbody><tr><td>hBTC</td><td>Base</td><td>cbBTC</td><td>75142b34-9345-48b3-80e5-765b81e75302</td><td>0x9C2dCDbDB3F0A0F628D1112bBCABD9AE75353df3</td><td>0x30eCa7f3d0c099385e830314c51bB9e95657b84D</td></tr><tr><td>oneUSD</td><td>Ethereum mainnet</td><td>USDC</td><td>e7f39a87-e5bb-4a11-b6a4-8a1ec710939f</td><td>0xbFdA6fB6E61BDeb2A2cE3bEfeBbD4939D0D828aa</td><td>0xC0E920eF95842161eA2Bf80E411dbD9B8fCb3091</td></tr></tbody></table>

Both vaults run on Ember Protocol's vault and deposit contracts, independently audited by OtterSec and Asymptotic, with formal verification by Asymptotic. The reports are published on Ember's security page, [ember.so/security](https://ember.so/security) (see also [Audits](https://docs.syntetika.io/audits.md)).
