Join our community of builders on

Telegram!Telegram

Signs data using the specified relayer.

Development Documentation

You're viewing documentation for unreleased features from the main branch. For production use, see the latest stable version (v1.1.x).
POST
/api/v1/relayers/{relayer_id}/sign
AuthorizationBearer <token>

In: header

Path Parameters

relayer_idstring

The unique identifier of the relayer

messagestring

Response Body

curl -X POST "https://loading/api/v1/relayers/string/sign" \  -H "Content-Type: application/json" \  -d '{    "message": "string"  }'
{
  "data": {
    "r": "string",
    "s": "string",
    "sig": "string",
    "v": 0
  },
  "error": "string",
  "metadata": {
    "logs": [
      {
        "level": "log",
        "message": "string"
      }
    ],
    "traces": [
      null
    ]
  },
  "pagination": {
    "current_page": 0,
    "per_page": 0,
    "total_items": 0
  },
  "success": true
}
{
  "data": null,
  "message": "Bad Request",
  "success": false
}
{
  "data": null,
  "message": "Unauthorized",
  "success": false
}
{
  "data": null,
  "message": "Not found",
  "success": false
}
{
  "data": null,
  "message": "Too Many Requests",
  "success": false
}
{
  "data": null,
  "message": "Internal Server Error",
  "success": false
}