Step 2: Setting configurations
Creating an API Key for OneBalance API
Currently, OneBalance provides applications with server-side authorization to access its APIs. For detailed information, refer to the OneBalance API Swagger documentation.
Note: Please contact us to request access to the OneBalance APIs.
Tokens and Chains
Here, you can find the endpoints for supported chains and tokens. The application can specify the chains and tokens it wishes to work with.
The list of supported chains is continually expanding. Please reach out to us to check for the latest updates.
For tokens, the application has two options:
Use Existing Token Lists: We provide default versions of tokens that are considered fungible with each other across different chains.
Define Custom Token Lists: The application can create its own list of tokens. For example, the app might treat different stablecoins on various chains as the same token and aggregate them into a single balance for spending.
Currently, this customization is handled on a per-application basis. Please reach out to have this setup tailored for your needs.
Orderflow monetisation for application (coming soon)
The application can configure the fee for each user transaction.
The fee payment transaction is incorporated into the UserOp on either the source or destination chain. It is included in the quote calculation and paid in the token used for the transaction.
Gas Abstraction
We support two gas payment models:
Gas Sponsorship: The application covers gas costs.
Quote-Inclusive Gas Payment: Gas costs are included in the quote (coming soon).
Note: The gas is fully abstracted from the users in either case, and the application does not require additional development to enable it.
Last updated