Programmatic Signatures (for Developers)

Creates digital signatures using the developer's (your) asymmetric key pair. For signing users' messages, use User Signatures instead.

Request

The bigint that needs to be signed is converted to a big-endian byte array and then converted to a hex string which is sent in the API request body in the message field.

Response

The response contains the signature which is a 64-byte compressed EdDSA signature in hex format as defined in RFC 8032.

This is what the response looks like:

{
    "status": "SUCCESS",
    // 64-byte compressed EdDSA signature in hex format
    "signature": "0x20ba78dcc23893aefaa3c8c2c9d99598831265e3ce32638d3cfda6c4d2028c8ade8b897c9d4542259204224ff59b72f7fea835727df8cee40cafd3a6d101ff02"
}

🚧

Api Error Status

You can find the error status returned by the API here.

© Copyright 2024, Passbird Research Inc.