Create Signature
Warning: This API has been deprecated. Please use Wallets. Contact your sales representative if you require additional blockchain support.
POST /public-keys/{PublicKeyId}/signatures
Signs the message in the hash
field corresponding to the specified PublicKey
. Note the request may be asynchronous - call GetSignatureById to check status and get the associated signature components once complete.
User action signature required. See User Action Signing for more information.
Request headers required. See Request Headers for more information.
Authentication required. See Authentication Headers for more information.
Required Permissions
Name | Conditions |
---|---|
| Always Required |
Triggers
Policy Engine for Policies with a CreatingSignature
activityKind
.
Parameters
Path parameters
Path parameter | Description |
---|---|
| Unique identifier of the |
Request body
Request body fields | Required/Optional | Description | Type |
---|---|---|---|
| Required | Any message to sign. Usually a transaction hash. | String |
Note: Any size message can be signed. For ECDSA signatures, first hash the message with SHA256 and then pass the result in the hash
body parameter (exactly 32 bytes are required as input). For EdDSA signatures, the original message is sent in the hash
parameter and accepted regardless of length.
Request example
Response
Response example
Requests will normally return status Pending. Call GetSignatureById to check status and get the associated signature components (r
and s
) once Executed
(for a mathematical explanation of the signature components, see Wikipedia). The v
component of the signature is returned in the recid
.
Last updated