We refreshed our doc site!

Bookmarked links may have changed

Read release notes

signMessage

Web3 Services
Compliance Engine

Sign message

POSThttps://api.circle.com/v1/w3s/developer/sign/message

Sign the EIP-191 message from a specified developer-controlled wallet. Please note that not all the Dapps currently support Smart Contract Account (SCA), the difference between EOA and SCA can be found in the account types guide, and you can check the list of Dapps that support SCA: https://eip1271.io/.

Body parameters
entitySecretCiphertext
byte
Required

A base64 string expression of the entity secret ciphertext. The entity secret should be encrypted by the entity public key. Circle mandates that the entity secret ciphertext is unique for each API request.

message
string
Required

The user friendly message that needs to be signed. If it is a hex string, encodedByHex needs to be TRUE. The hex string should start with “0x” and have even length.

walletId
uuid
Required

System-generated unique identifier of the resource.

encodedByHex
boolean

Indicator of whether the input message is encoded by hex. If TRUE, then the message should be a hex string. By default, it is False.

memo
string

The human readable explanation for this sign action. Useful for presenting with extra information.

Response
RequestChoose a language
ResponseChoose an example
1{
2  "data": {
3    "signature": "0x977c17f82d8b042b67b09d0e61e7d324f050cb000c17a08..."
4  }
5}
Did this page help you?
© 2023-2024 Circle Technology Services, LLC. All rights reserved.