Documentation - Notus API

This endpoint queues to execution a user operation on the blockchain, like a swap quote or a transfer. The execution occurs asynchronously as it waits to be included in a block. You can check the status by using the returned hash in the history endpoint or with our webhooks.

Authorization

x-api-key

x-api-key<token>

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

userOperationHash?string

Unique identifier for the swap quote, required to execute the transaction.

Match^0x[a-fA-F0-9]{64}$

quoteId?string

Deprecated

DEPRECATED: Use userOperationHash instead. Will be ignored if userOperationHash is used.

Match^0x[a-fA-F0-9]{64}$

signature*string

The signature of the transaction, required to execute the transaction.

Match^0x([a-fA-F0-9]{2})*$

authorization?string

The signature of the authorization, required to execute the first transaction of an EIP-7702 wallet. If the authorization field was null in the operation you requested, then you don't have to send this.

ATTENTION: viem's signAuthorization() returns the signature as {r, s, yParity} values. Use plain sign() with the returned hash field instead that already returns the signature in the expected format. Or call serializeSignature() after signAuthorization() to serialize it for this endpoint.

Match^0x([a-fA-F0-9]{2})*$

limitOrderSignature?string

Optional signature for limit orders. Required only when the quote response included typedData.

Match^0x([a-fA-F0-9]{2})*$

rwaOrderSignature?string

Signature over the RWA order typed data. Required when the quote came from an RWA cross-chain provider whose response included typedData. The order is submitted to the destination order book before the user operation executes.

Match^0x([a-fA-F0-9]{2})*$

rwaApproveUserOperationHash?string

Every RWA buy: hash of the sponsored destination-chain approve operation returned by the quote as rwaApproveUserOperation.userOperationHash. Each buy grants an exact allowance for that order, consumed by its fill — omitting this leaves the order unfillable.

Match^0x[a-fA-F0-9]{64}$

rwaApproveSignature?string

Every RWA buy: signature over rwaApproveUserOperationHash. The approve operation is submitted before the swap user operation executes.

Match^0x([a-fA-F0-9]{2})*$

rwaApproveAuthorization?string

EIP-7702 authorization signature for the approve operation. Required when the quote response included rwaApproveUserOperation.authorization.

Match^0x([a-fA-F0-9]{2})*$

stellarDepositQuoteId?string

Stellar savings funding: deposit.quoteId from /crypto/stellar/defindex/funding-quote. The API parks the signed authorization and submits the deposit once the bridged USDC lands on Stellar.

Match^0x[a-fA-F0-9]{64}$

stellarDepositSignedXdr?string

Stellar savings funding: the Soroban authorization entry from deposit.xdr, signed by the Stellar account and base64 encoded. Only the signature may be added — the invocation, nonce and expiration must stay exactly as quoted.

Match^$|^(?:[0-9a-zA-Z+/]{4})*(?:(?:[0-9a-zA-Z+/]{2}==)|(?:[0-9a-zA-Z+/]{3}=))?$

Response Body

`application/json`

curl -X POST "https://example.com/api/v1/crypto/execute-user-op" \  -H "Content-Type: application/json" \  -d '{    "signature": "0xeecdd469465113db97d2d57949c581a080a4e7d7c528187ffc80e4f55ca68e083dcda2338666db182417608b971f5237c5807d67c7515e52f9ffe045e775ec791b"  }'

{  "userOperationHash": "0x2aac7a66d5331454eafc9b981be3596ad08a40dad24883e3b9c4a5362cd7f7e1",  "userOpHash": "0x2aac7a66d5331454eafc9b981be3596ad08a40dad24883e3b9c4a5362cd7f7e1",  "estimatedExecutionTime": "2026-04-12T14:49:12.762Z"}

Execute User Operation

Authorization

Request Body

Response Body

202application/json

400application/json

403application/json

404application/json

500application/json

`application/json`

`application/json`

`application/json`

`application/json`

`application/json`