There are 2 sides of the Absinthe APIs.

  1. Registering wallets + social identities under a user profile (roll your own auth)
  2. Fetching points data like:
    • user points + achievements
    • leaderboard data

​
Registering Identities

There are three tables you need to be concerned with: users, wallets, and socials.

  • Each user profile is grouped together under a user.
  • A user can have up to 11 wallets connected to it.
  • A user can have at most 1 social identity connected PER provider (1 twitter, 1 discord, etc).

You can test-drive the API in our interactive graphql playground here.

You will need an API key to set in an authorization header. If you don’t have one yet, reach out to the Absinthe team here to get you one.

If your bearer token is not configured for backend access, these API calls WILL NOT FAIL, they will simply return null. Please contact the Absinthe team to ensure that your API key is configured for backend access.

​
Setting The Authorization Header

Before being able to introspect the schema through our interactive graphql playground or through a direct call, you will need to set the API key as an authorization header via this format:

{"Authorization": "Bearer <INSERT_KEY_HERE>"}

​
Endpoint URL

https://gql3.absinthe.network/v1/graphql

​
Registering Users

​
Fetching Data Per User

You can fetch user data from the dagster_computed_points_log, dagster_computed_achievements, and dagster_computed_aggregated_scores.

  1. The computed_points_log is a breakdown of each users points earning entries.
  2. The computed_achievements is a breakdown of which achievement each user earned and how much bonus each achievement gives.
  3. The computed_aggregated_scores is a breakdown of each users total scores and their referral score.
PricingOverview