API Overview
The existing integrator API is https://api.blockfinax.com/v1. Its current Swagger UI and OpenAPI schema describe EVM integrations. They do not currently implement the Stellar routes below.
Stellar extension
The planned namespace is /v1/stellar. It preserves the current split between public reads, unsigned transaction builders, and an optional relay. Network selection uses testnet or mainnet, not an invented numeric EVM chain ID. JSON asset amounts and fixed-point prices are decimal integer strings.
| Group | Planned route family | Responsibility |
|---|---|---|
| Meta | /v1/stellar/networks, /v1/stellar/fees/:network | Manifests and fee policies |
| Hedge reads | /v1/stellar/hedge/.../:network/... | Events positions deposits capacity and payouts |
| Oracle reads | /v1/stellar/oracle/.../:network/... | Sources policy submissions and fixing |
| Governance | /v1/stellar/governance/.../:network | Roles code hashes upgrades and delays |
| Transaction build | /v1/stellar/tx/hedge/... | Simulated unsigned XDR and authorizations |
| Relay | /v1/stellar/tx/broadcast | Submit signed XDR and track the receipt |
| Pricing | /v1/stellar/pricing/quote | Adapt the existing engine and optional attestation |
Response envelope
Preserve data and optional meta on success, and error.code, error.message, and optional error.details on failure. Every Stellar response carries its network context. Reads expose an as-of ledger and indexed timestamp rather than pretending an indexer's cached state is always the current contract state.
Compatibility
Existing /v1/hedge, /v1/tx, and numeric chainId integrations remain EVM interfaces. A caller selects the Stellar adapter explicitly. Deployment addresses stay unavailable until a verified manifest is published. We will publish contract IDs and runnable examples with the verified deployment.