Persistent deposit address
This API is currently work in progress.
API key generated at https://studio.aurora.dev
To specify the asset the user receives, you can either:
- Pass a token symbol in
destinationAsset(e.g. "USDC") together withdestinationChain(e.g. "base"). The API resolves the symbol to an asset ID on that chain. - Or pass an asset ID directly in
destinationAsset(e.g. "nep141:base-0x...omft.near").destinationChainis still required to locate it.
When a symbol matches more than one token on the same destinationChain, the request fails with 400 and an error listing the matching asset IDs ("Multiple tokens with symbol ... Use one of the asset IDs instead: ..."). In that case, retry with the specific asset ID you want.
Target address on the destination chain. Funds deposited to the returned address will ultimately route to this address.
0x2527D02599Ba641c19FEa793cD0F167589a0f10DIdentifier of the user the deposit address is generated for (e.g. their ID in the system). A unique deposit address is generated and persisted per (sender, recipient, depositChain), so incoming deposits can be attributed to a specific user.
some-user-idChain the user deposits FROM (the chain of the returned deposit address). Short code matching the widget config Chains enum, e.g. "arb" for Arbitrum.
arbPossible values: Chain the user receives funds ON. Used to resolve destinationAsset when it is provided as a symbol. Short code matching the widget config Chains enum, e.g. "base" for Base.
basePossible values: Asset the user wants to receive on destinationChain. Accepts either a token symbol (e.g. "USDC") or an asset ID (e.g. "nep141:base-0x...omft.near"). When a symbol is used and more than one token shares that symbol on destinationChain, the request is rejected with 400 and the caller must switch to the asset ID.
USDCPersistent deposit address generated or fetched from cache
Persistent deposit address generated or fetched from cache
Chain-specific deposit address. Sending any supported asset on this chain to this address will deposit funds into the NEAR Intents account associated with recipient.
0x76b4c56085ED136a8744D52bE956396624a730E8Default Response
Application key is not assigned or no token matches destinationAsset on destinationChain
Internal Server Error - Failed to call upstream services
Last updated
