The Signature API endpoint (try it out here) receives a raw Signature Request object containing the following fields:
|SignMethod enum||(Required) The RPC method being invoked|
|array of strings||(Required) An array of strings, each representing an input to the RPC method. Depending on which |
|string||(Optional) URL of the website or dapp that originated the transaction. Used for risk assessment.|
The Signature API endpoint returns an object containing the following fields.
Base Response Fields: these fields are present on both Transaction and Signature API responses.
|string||Required. A one-sentence summary of this transaction.|
|RiskResult||Required. Results of risk evaluation|
|AssetChange||Required. List of assets leaving or entering the signer's wallet|
|string||Optional. List of error messages. Present if any errors were encountered.|
Signature-specific response fields: these fields are present only on Signature API responses.
|RPCMethod||Required. RPC Method type string enum. There will rarely be new RPC method types added.|
|SignatureType||Required. Signature type string enum. More signature types will be added as Stelo adds support for more protocols.|
|string||Required. Address of signer.|
|string||Optional. Plaintext message being signed. Always present for |
|JSON||Optional. Parsed JSON object being signed. Always present when |
|Seaport||Optional. Details of Seaport message being signed. Always present when |
|ParsedTransaction||Optional. Details of embedded transaction (eg. for a Gnosis safe transaction). Always present when |