Skip to main content
GET
/
2025-06-09
/
wallets
/
{walletLocator}
/
signatures
/
{signatureId}
Get Signature
curl --request GET \
  --url https://staging.crossmint.com/api/2025-06-09/wallets/{walletLocator}/signatures/{signatureId} \
  --header 'X-API-KEY: <x-api-key>'
{
  "id": "sig-b984491a-5785-43c0-8811-45d46fe6e520",
  "type": "message",
  "chainType": "evm",
  "walletType": "smart",
  "status": "awaiting-approval",
  "params": {
    "message": "Hello, world!",
    "signer": {
      "type": "external-wallet",
      "address": "0xB17Ea8d34078424B9d7D126E444d5F2C3CC5c81E",
      "locator": "external-wallet:0xB17Ea8d34078424B9d7D126E444d5F2C3CC5c81E"
    },
    "chain": "polygon"
  },
  "approvals": {
    "pending": [
      {
        "signer": {
          "type": "external-wallet",
          "address": "0xB17Ea8d34078424B9d7D126E444d5F2C3CC5c81E",
          "locator": "external-wallet:0xB17Ea8d34078424B9d7D126E444d5F2C3CC5c81E"
        },
        "message": "Hello world!"
      }
    ],
    "submitted": []
  },
  "createdAt": "2024-01-01T00:00:00Z"
}

Headers

​
X-API-KEY
string
required

API key required for authentication

Path Parameters

​
walletLocator
string
required

A wallet locator can be of the format:

  • <walletAddress>
  • email:<email>:<chainType>[:<walletType>][:alias:<alias>] (walletType defaults to 'smart')
  • userId:<userId>:<chainType>[:<walletType>][:alias:<alias>] (white label user example)
  • phoneNumber:<phoneNumber>:<chainType>[:<walletType>][:alias:<alias>]
  • twitter:<handle>:<chainType>[:<walletType>][:alias:<alias>]
  • x:<handle>:<chainType>[:<walletType>][:alias:<alias>]
  • me:<chainType>[:<walletType>][:alias:<alias>] (Use when calling from the client side with a client API key)
  • chainType[:<walletType>]:alias:<alias>
​
signatureId
string
required

Response

The signature has been successfully retrieved.

Complete signature response including status, signing requirements, and wallet type specific data

​
id
string
required

Unique identifier for the signature

​
type
enum<string>
required

The type of signature

Available options:
message,
typed-data
​
chainType
enum<string>
required

The blockchain type of the wallet

Available options:
evm,
solana,
aptos,
sui,
stellar
​
walletType
enum<string>
required

The wallet type (smart or mpc)

Available options:
smart,
mpc
​
status
enum<string>
required

Current status of the signature

Available options:
awaiting-approval,
pending,
failed,
success
​
params
object
required

Type-specific signature parameters Parameters for a message signature

  • Message signature parameters
  • Typed data signature parameters
​
createdAt
required

ISO timestamp when the signature was created ISO 8601 formatted timestamp

Example:

"2024-01-01T00:00:00.000Z"

​
approvals
object

Complete approval data including requirements, pending and submitted signatures

​
completedAt

ISO timestamp when the transaction reached finality ISO 8601 formatted timestamp

Example:

"2024-01-01T00:00:00.000Z"

​
error
any

Error message if the signature fails

​
outputSignature
string

The wallet's output signature of the request