Practical overview
When it fits
Use it when a Web3 application needs Velora API access for aggregated DEX liquidity, rate retrieval or swap-related integration work.
Who it is for
- Developers building decentralized applications.
- Teams adding token swaps or trading interfaces to Web3 products.
- Engineers creating server-side Velora API integrations.
Documented uses
- Retrieve rates and routes for token swaps.
- Access liquidity aggregated across multiple DEX markets.
- Build swap transaction parameters.
- Configure approval and signing workflows through supported provider integrations.
- Build Delta v2 orders through the server-side API flow.
Requirements & limits
The repository is public, active and open source under the MIT license. The documented installation method uses pnpm. No pricing or account requirements are documented here.
- Choose the simple SDK when the application primarily needs API-query methods; provider options add approval and signing capabilities.
- Choose the full or partial construction patterns when the integration needs broader composition or tighter bundle-size control.
- Account for the v10 breaking changes, including server-side Delta v2 order building and renamed or removed order APIs.
- The SDK is TypeScript-based and documents compatibility with web3, ethers and viem integrations.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Construct a minimal rate-query SDK
Set up the minimal SDK variant with a chain ID and an HTTP request implementation so an application can query the Velora API.
Before you start
- A TypeScript project using the Velora SDK package.
- A chain ID.
- Axios or a fetch implementation such as window.fetch.
- The documented package installation command: pnpm add @velora-dex/sdk.
Steps
Install the package with pnpm add @velora-dex/sdk.
Import constructSimpleSDK from the package and provide a chainId together with axios or fetch.
Call the SDK's swap.getRate method with source token, destination token, amount, user address and swap side parameters.
Use the returned price route as the input for the documented swap transaction-building flow.
Expected outcome
The application has a minimal SDK instance that can query a Velora swap rate and obtain a price route for the documented swap workflow.
Construct a signer-enabled SDK
Configure the SDK with an ethers, viem or web3 provider so the documented approval and order-signing capabilities are available.
Before you start
- A chain ID and an HTTP request implementation.
- A provider, signer or client compatible with ethers, viem or web3.
- The relevant provider or contract constructor described in the README.
- An account address.
Steps
Create provider options for ethers, viem or web3 using the documented fields.
Pass those provider options as the second argument to constructSimpleSDK, or construct a full SDK with a fetcher and contract caller.
Use the resulting SDK for the documented approval or order-signing methods.
For a token approval, call approveToken with an amount and token address, then wait for the transaction according to the provider workflow.
Expected outcome
The application has a provider-aware SDK configuration for the documented approval, signing and related contract interactions.
Guide limitations
- Delta v2 orders are built server-side, and v10 removes the former per-family Delta signers.
Compare options for DEX swap integration
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Velora SDK | Retrieve rates and routes for token swaps. | Cloud, Server, Web | The repository is public, active and open source under the MIT license. The documented installation method uses pnpm. No pricing or account requirements are documented here. |
| VIA SDK | Find swap or bridge routes using source and destination chains, token addresses, and an amount. | Web | The package is installed through npm and the documented client uses an API key. The README says the default key is limited to one request per second per IP and directs developers seeking higher limits to contact VIA. |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 1 October 2026
- Original website title
- VeloraDEX/sdk · Official homepage title · retained in its source language

