Available Queries

Github Activity

Tier: free

Max lag: A few hours. This metric is depended on an external service - when data is uploaded there, it is available in this query after a few minutes.

Max resolution: 1min

Returns the number of GitHub events generated by a given project repositories. Each project has one or more repositories/organizations that are tracked. A longer description of how the activity is being tracked can be found in this article: Tracking GitHub activity of crypto projects — introducing a better approach

Parameters:

Example:

{
  githubActivity(slug:"santiment", from:"2019-01-01T00:00:00Z", to:"2019-06-01T00:00:00Z", interval:"1d") {
    datetime
    activity
  }
}

Run in explorer

Dev Activity

Tier: free

Max lag: A few hours. This metric is depended on an external service - when data is uploaded there, it is available in this query after a few minutes.

Max resolution: 1min

Returns the number of GitHub events generated by a given project repositories that are connected with development actions. Each project has one or more repositories/organizations that are tracked. A longer description of how the activity is being tracked can be found in this article: Tracking GitHub activity of crypto projects — introducing a better approach

The difference with the githubActivity API is that the actions counted in this API exclude events that are considered non-development related. These are:

• Comments on issues
• Issues created and closed
• Creating of forks
• Comments on commits
• People following an issue
• Downloading releases
• Watching a repository
• Project management events

This metric becomes useful if you compare projects that use the github functionality for project management and issue tracking. They are going to have larger githubActivity, compared to projects that use github only for code, as they will generate a lot of events related to issues and tasks.

Parameters:

Example:

{
  devActivity(
    slug: "santiment"
    from: "2019-01-01T00:00:00Z"
    to: "2019-06-01T00:00:00Z"
    interval: "1d") {
      datetime
      activity
  }
}

Run in explorer

History Price

Tier: free

Max lag: A few minutes

Max resolution: 5min Return the price in USD and BTC, marketcap in USD and volume in USD.

Parameters:

Example:

{
  historyPrice(
    slug: "santiment"
    from: "2019-01-01T00:00:00Z"
    to: "2019-06-01T00:00:00Z"
    interval: "1d") {
      datetime
      priceUsd
      priceBtc
      marketcap
      volume
  }
}

Run in explorer

OHLC (Open-High-Low-Close)

Tier: free

Max lag: A few minutes

Max resolution: 5min

Returns the open, high, low and close prices in USD for the given interval.

Parameters:

Example:

{
  ohlc(
    slug: "santiment"
    from: "2019-01-01T00:00:00Z"
    to: "2019-06-01T00:00:00Z"
    interval: "1d") {
      datetime
      openPriceUsd
      highPriceUsd
      lowPriceUsd
      closePriceUsd
  }
}

Run in explorer

History Twitter Data

Tier: free

Max lag: 7 hours

Max resolution: 7 hours

Returns the number of twitter followers of the project’s twitter account over time.

Parameters:

Example:

{
  historyTwitterData(
    slug: "santiment"
    from: "2019-01-01T00:00:00Z"
    to: "2019-06-01T00:00:00Z"
    interval: "1d") {
      datetime
      followersCount
  }
}

Run in explorer

Social Volume

Tier: free

Max lag: A few hours. This metric is depended on an external service - when data is uploaded there, it is available in this query after a few minutes.

Max resolution: 1min

TODO DESCRIPTION

Parameters:

Example:

{
  socialVolume(
    slug: "santiment"
    from: "2019-01-01T00:00:00Z"
    to: "2019-02-01T00:00:00Z"
    interval: "1h"
    socialVolumeType: DISCORD_DISCUSSION_OVERVIEW) {
      datetime
      mentionsCount
  }
}

Run in explorer

Social Dominance

Tier: free

Max lag: A few hours. This metric is depended on an external service - when data is uploaded there, it is available in this query after a few minutes.

Max resolution: 1min

TODO DESCRIPTION

Parameters:

Example:

{
  socialDominance(
    slug: "santiment"
    from: "2019-01-01T00:00:00Z"
    to: "2019-02-01T00:00:00Z"
    interval: "1h"
    source: ALL) {
      datetime
      dominance
  }
}

Run in explorer