Tickets

Return status information about tickets or the server itself. For operations that cannot complete immediately, the system returns a ticketId. You can look up this ticketId to determine the true status of the operation.

Check system status

Ensure that you can make a connection to the Wallet API.

Jump to examples ↓

GET /system/status

Responses

200
You have successfully established a connection with the server.
Response body:
- Content-Type: application/json
  OBJECT PROPERTIES
  - Hello string
    A “Hello World” response tells you that everything is Ok.
    Possible values: World

Examples

GET /v1/system/status HTTP/1.1

HTTP/1.1 200 OK
Content-Type: application/json

{
    "Hello": "World"
}

Get ticket status

Get the status of a ticket. Some operations can’t complete immediately and return a ticketId. Use this item to determine the true status of the operation.

Jump to examples ↓

GET /ticket/{ticketId}

Security:

httpBasic

Path parameters:

ticketId stringREQUIRED
The ticket you want to know the status of.

Responses

200
Returns the status of a ticket.
Response body:
- Content-Type: application/json
  OBJECT PROPERTIES
  - ID integer
    The identifier of the ticket.
  - children object
  - createdAt string
    The date and time when the item was created.
  - status string
    The status of the ticket.

Examples

GET /v1/ticket/123 HTTP/1.1
Authorization: Basic <Base64 key>

HTTP/1.1 200 OK
Content-Type: application/json

{
   "Status": "COMPLETED",
   "createdAt": "2013-03-28 18:18:36.0",
   "ID": 123,
   "children": {
      "...": "..."
   }
}