OZozav
Network Transfers

Move your own USDC to another network

Not callable (coming_soon). No API key can be issued with the network_transfers:write scope this route requires, so it answers 403 INSUFFICIENT_SCOPE for every key. The contract below shows the request and the response.

Moves USDC you already hold from one network to another, in the same wallet. It is not a payment: origin and destination are the same holder.

  • Answers 202. The transfer burns on the origin network under a two-party signing quorum, waits for attestation and then mints on the destination, which takes minutes. The response carries an id; read the state from GET /network-transfers/{transfer_id}.
  • One transfer in flight per source network. A second request while one is in flight answers 202 with the transfer already running and duplicate: true.
  • The holder comes from your key, never from the body.
  • The amount is a decimal integer string in the asset's smallest unit.
post/network-transfers

Request

  • Base URL
    https://developers.ozav.io/v2
  • Auth
    • API key in header X-API-Key
    • or HTTP bearer

Request body

source_chainstring required
destination_chainstring required
assetstring required

Only USDC crosses today.

amountstring required

Decimal integer string, smallest unit of asset. Never a float.

Example request

{
  "source_chain": "ethereum",
  "destination_chain": "base",
  "asset": "USDC",
  "amount": "5000000"
}

Response

Accepted. Read the state with GET /network-transfers/{transfer_id}. duplicate is true when a transfer was already in flight for that source network; the transfer returned is that one.

duplicateboolean

Changes

No recorded changes to this operation across all 1 revision of this API.