Sign

Submits a request to sign an Ethereum message. Uses private keys securely stored within the custody system. The signing process is asynchronous, as it requires approval from the wallet owner(s) via our Proof of Action (PoA) mechanism.

POST /v1/signs

Request message signing (custody-based with callback)

cURL

curl --request POST \
  --url https://omnisafe.sandbox.ecrop.de/omni-safe/v1/signs \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "message": "SGVsbG8gV29ybGQh",
  "address": "0x...",
  "callbackUrl": "https://example.com/callback",
  "chainId": 1
}
'

202

{
  "requestId": "a1b2c3d4-e5f6-7890-1234-567890abcdef"
}

Authorizations

Authorization · string · header · required

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

Body

application/json

message · string

The message (Base64 encoded).

Example:

"SGVsbG8gV29ybGQh"

address · string

The user's wallet address.

Example:

"0x..."

callbackUrl · string

URL to receive the signing result via webhook.

Example:

"https://example.com/callback"

chainId · integer

Ethereum chain ID (EIP-155).

Example:

1

Response

202

application/json

Signing request accepted.

requestId · string

Unique ID of the signing request.

Example:

"a1b2c3d4-e5f6-7890-1234-567890abcdef"