List candle data

Get a list of candle data for a given candle ID. Candle IDs can be obtained by calling list-candle-intervals

Query Parameters

candleId string required

Candle ID to retrieve candle data for.

fromTimestamp int64

Timestamp in Unix nanoseconds to retrieve candles from.

toTimestamp int64

Timestamp in Unix nanoseconds to retrieve candles to.

pagination.first int32

Number of records to be returned that sort greater than row identified by cursor supplied in 'after'.

pagination.after string

If paging forwards, the cursor string for the last row of the previous page.

pagination.last int32

Number of records to be returned that sort less than row identified by cursor supplied in 'before'.

pagination.before string

If paging forwards, the cursor string for the first row of the previous page.

pagination.newestFirst boolean

Whether to order the results with the newest records first. If not set, the default value is true.

Responses

• 200
• 500
• default

---

A successful response.

application/json

Schema

Example (from schema)

---

Schema

candles object

Page of candle data and corresponding page information.

edges object[]

Page of candle data items and their corresponding cursors.

Array [

cursor string

Cursor that can be used to fetch further pages.

node object

Candlestick data, i.e. high, low, open, and closing prices for an interval of trading.

close string

Closing trade price.

high string

Highest price for trading during the candle interval.

lastUpdate int64

Timestamp in Unix nanoseconds for the point in time when the candle was last updated.

low string

Lowest price for trading during the candle interval.

notional uint64

Total notional value traded during the candle interval.

open string

Open trade price.

start int64

Timestamp in Unix nanoseconds for the point in time when the candle was initially created/opened.

volume uint64

Total trading volume during the candle interval.

]

pageInfo object

Page information that is used for fetching further pages.

endCursor string

End cursor.

hasNextPage boolean

Indicator if there is a next page.

hasPreviousPage boolean

Indicator if there is a previous page.

startCursor string

Start cursor.

{
  "candles": {
    "edges": [
      {
        "cursor": "string",
        "node": {
          "close": "string",
          "high": "string",
          "lastUpdate": "string",
          "low": "string",
          "notional": "string",
          "open": "string",
          "start": "string",
          "volume": "string"
        }
      }
    ],
    "pageInfo": {
      "endCursor": "string",
      "hasNextPage": true,
      "hasPreviousPage": true,
      "startCursor": "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"
}

GET /api/v2/candle

Request

Base URL

https://api.n00.testnet.vega.rocks

candleId — query required

fromTimestamp — query

toTimestamp — query

pagination.first — query

pagination.after — query

pagination.last — query

pagination.before — query

pagination.newestFirst — query

---truefalse

curl / cURL

curl -L -X GET 'https://api.n00.testnet.vega.rocks/api/v2/candle' \
-H 'Accept: application/json'

python / requests

curl -L -X GET 'https://api.n00.testnet.vega.rocks/api/v2/candle' \
-H 'Accept: application/json'

go / native

curl -L -X GET 'https://api.n00.testnet.vega.rocks/api/v2/candle' \
-H 'Accept: application/json'

nodejs / axios

curl -L -X GET 'https://api.n00.testnet.vega.rocks/api/v2/candle' \
-H 'Accept: application/json'