Get withdrawal

Get a withdrawal by its ID. A withdrawal's ID will be the SHA3-256 hash of the signature that the withdrawal was submitted with

Path Parameters

id string required

Withdrawal ID to retrieve data for.

Responses

• 200
• 500
• default

---

A successful response.

application/json

Schema

Example (from schema)

---

Schema

withdrawal object

Withdrawal matching the ID from the request.

amount string

Amount to be withdrawn. This field is an unsigned integer scaled to the asset's decimal places.

asset string

Asset to withdraw funds from.

createdTimestamp int64

Timestamp for when the network started to process this withdrawal.

ext object

Foreign chain specifics.

erc20 object

ERC20 withdrawal details.

receiverAddress string

Address into which the bridge will release the funds.

id string

Unique ID for the withdrawal.

partyId string

Unique party ID of the user initiating the withdrawal.

ref string

Reference which is used by the foreign chain to refer to this withdrawal.

status Status of the withdrawal

Possible values: [STATUS_UNSPECIFIED, STATUS_OPEN, STATUS_REJECTED, STATUS_FINALIZED]

Default value: STATUS_UNSPECIFIED

Status of the withdrawal.

txHash string

Hash of the foreign chain for this transaction.

withdrawnTimestamp int64

Timestamp for when the withdrawal was finalised by the network.

{
  "withdrawal": {
    "amount": "string",
    "asset": "string",
    "createdTimestamp": "string",
    "ext": {
      "erc20": {
        "receiverAddress": "string"
      }
    },
    "id": "string",
    "partyId": "string",
    "ref": "string",
    "status": "STATUS_UNSPECIFIED",
    "txHash": "string",
    "withdrawnTimestamp": "string"
  }
}

An internal server error

application/json

Schema

Example (from schema)

---

Schema

code int32
details object[]
Array [
@type string
A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in path/google.protobuf.Duration). The name should be in a canonical form (e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme http, https, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows:
• If no scheme is provided, https is assumed.
• An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
• Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com.
Schemes other than http, https (or the empty scheme) might be used with implementation specific semantics.
]
message string

{
  "code": 0,
  "details": [
    {
      "@type": "string"
    }
  ],
  "message": "string"
}

An unexpected error response.

application/json

Schema

Example (from schema)

---

Schema

code int32
details object[]
Array [
@type string
A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in path/google.protobuf.Duration). The name should be in a canonical form (e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme http, https, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows:
• If no scheme is provided, https is assumed.
• An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
• Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com.
Schemes other than http, https (or the empty scheme) might be used with implementation specific semantics.
]
message string

{
  "code": 0,
  "details": [
    {
      "@type": "string"
    }
  ],
  "message": "string"
}

Loading...