List oracle data

Get a list of all oracle data that have been broadcast to any market

Query Parameters

oracleSpecId string

Oracle spec ID to list data for.

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

oracleData object

Page of seen oracle data and corresponding page information.

edges object[]

Page of oracle data and their corresponding cursors.

Array [

cursor string

Cursor that can be used to fetch further pages.

node object

Data that was received from an external oracle.

externalData object

data object

Data describes valid source data that has been received by the node. It represents both matched and unmatched data.

broadcastAt int64

Timestamp in Unix nanoseconds for when the data was broadcast to the markets with a matching spec. It has no value when the data did not match any spec.

data object[]

Array [

name string

Name of the property.

value string

Value of the property.

]

error string

Error message if the data could not be sourced.

matchedSpecIds string[]

matched_specs_ids lists all the specs that matched this data. When the array is empty, it means no spec matched this data.

metaData object[]

Array [

name string

Name of the property.

value string

Value of the property.

]

signers object[]

Array [

ethAddress object

In case of an open oracle - Ethereum address will be submitted.

address string

pubKey object

List of authorized public keys that signed the data for this source. All the public keys in the data should be contained in these public keys.

key string

]

]

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.

{
  "oracleData": {
    "edges": [
      {
        "cursor": "string",
        "node": {
          "externalData": {
            "data": {
              "broadcastAt": "string",
              "data": [
                {
                  "name": "string",
                  "value": "string"
                }
              ],
              "error": "string",
              "matchedSpecIds": [
                "string"
              ],
              "metaData": [
                {
                  "name": "string",
                  "value": "string"
                }
              ],
              "signers": [
                {
                  "ethAddress": {
                    "address": "string"
                  },
                  "pubKey": {
                    "key": "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"
}

Loading...