Skip to main content
POST
Sign an Aleo function-call request with a WAAS wallet

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

environmentId
string
required

ID of the environment

Required string length: 36
Pattern: ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Example:

"95b11417-f18f-457f-8804-68e361f9164f"

walletId
string
required

UUID of the wallet

Required string length: 36
Pattern: ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Example:

"95b11417-f18f-457f-8804-68e361f9164f"

Body

application/json

Sign Aleo Request

payload
object
required

Aleo EdBls12377 sign request payload (function_id, is_root, program_checksum, inputs)

Response

SSE stream for the Aleo sign-request ceremony. The response is text/event-stream (NOT JSON): clients consume it via EventSource and receive room_created and signed events; the signed request is delivered to the initiating client (iframe) via Sodot's relay.

The response is of type string.

Last modified on July 17, 2026