The Passive Deposit/Withdrawal Service provides an API for moving assets between supported blockchain networks and NEAR Intents. Use it to deposit tokens into the protocol and withdraw them to external chains.Documentation Index
Fetch the complete documentation index at: https://docs.near-intents.org/llms.txt
Use this file to discover all available pages before exploring further.
JSON-RPC Endpoint
POST:https://bridge.chaindefuser.com/rpc
There is an SDK for integrating this service: Intents SDK on GitHub. This SDK is under active development and may introduce breaking changes.
How it works
API Reference
supported_tokens
Returns a list of tokens supported by the service for each network.Optional chain filter (e.g.,
["eth:1", "btc:mainnet"])Response fields
Response fields
For each token:
defuse_asset_identifier- Unique asset ID (format:CHAIN_TYPE:CHAIN_ID:ADDRESS)near_token_id- Token ID in the NEAR blockchaindecimals- Token precisionasset_name- Token namemin_deposit_amount- Minimum amount to trigger transfermin_withdrawal_amount- Minimum amount for withdrawalwithdrawal_fee- Fee charged for withdrawalsstandard- Token standard (for examplenep141ornep245)intents_token_id- Intents token identifiermulti_token_id- Multi-token identifier for supported multi-token assets
Request
Response
deposit_address
Returns the address for depositing supported tokens or native currency.Your NEAR Intents account (e.g.,
user.near)Network type and chain ID (e.g.,
eth:42161 for Arbitrum, btc:mainnet for Bitcoin)Optional. For Stellar, set this to
MEMO.Request
Response
recent_deposits
Returns information on recent deposits for an account.Your NEAR Intents account
Optional network type and chain ID
Optional status filter:
PENDING, CREDITED, COMPLETED, or FAILEDOptional page size. Defaults to
20 and is capped at 100.Optional pagination offset. Defaults to
0.Response fields
Response fields
For each deposit:
tx_hash- Transaction hash (EVM networks only)mint_tx_hash- Mint transaction hash on NEARchain- Network type and chain IDdefuse_asset_identifier- Token identifiernear_token_id- Token identifier on NEARdecimals- Token decimalsamount- Asset amountaccount_id- NEAR Intents accountaddress- Deposit addressstatus-PENDING,CREDITED,COMPLETED, orFAILEDcreated_at- Deposit creation timefrom- Sender address
Request
Response
withdrawal_status
Returns the status of a withdrawal.Hash of the NEAR transaction where
ft_burn event occurredResponse fields
Response fields
status-COMPLETED,PENDING,FAILED,NOT_FOUND,AWAITING,REJECTED,RETURNING, orRETURNEDdata.tx_hash- Burn transaction hash on NEARdata.transfer_tx_hash- Transfer transaction hash on destination chaindata.chain- Network type and chain IDdata.defuse_asset_identifier- Token identifierdata.near_token_id- Token identifier on NEARdata.decimals- Token decimalsdata.amount- Asset amountdata.account_id- User accountdata.address- Token address saved for the withdrawal recorddata.created_at- Withdrawal creation timedata.withdrawal_fee- Fee charged for the withdrawaldata.withdraw_amount- Amount sent to destination after fee handling
Request
Response
recent_withdrawals
Returns recent withdrawals for an account.Your NEAR Intents account
Optional network type and chain ID
Request
Response
notify_deposit
Optional method to notify the service about your deposit for faster processing.Network type and chain ID (for example
eth:8453, near:mainnet, or stellar:mainnet)Address you received from the API
Hash of your deposit transaction
Required when
chain is near:mainnet.Required when
chain is stellar:mainnet. Max length: 32.Request
Response
withdrawal_estimate
Estimate fees for a withdrawal transaction.Blockchain network (e.g.,
eth:1)Token identifier (e.g.,
eth.omft.near)Recipient address
Response fields
Response fields
tokenAddress- Token contract addressuserAddress- User’s addresswithdrawalFee- Estimated feewithdrawalFeeDecimals- Fee decimal precisiontoken- Token information
Request
Response
hot_omni_withdraw
Triggers a hot OMNI withdrawal flow.Your NEAR Intents account
NEAR transaction hash for the withdrawal request
Recipient address on destination chain
Destination chain ID
Request
Response
The
hot_omni_withdraw result is passed through from backend services and may include additional fields over time.attestation
Fetches an attestation payload/signature used by downstream integrations.Payload to be attested
Network type for attestation context
Request
Response