mutation IssueOffChainPoints {
  insert_api_points_one(object: {
    account_id: "0xB58621209Dc0b0c514E52a6D9A165a16ae95e4f7", 
    identity_type: EVM_ADDRESS, 
    amount: "10", 
    reg_event_id: "ebffbc49-fa89-4e73-ab40-4e8be59331fd", 
    metadata: {
      transaction_id: "tx_12345",
      source: "twitter-engagement",
      details: {
        tweet_id: "1234567890",
        action: "retweet",
        timestamp: "2023-10-15T14:30:00Z"
      }
    }
  }) {
    id
    amount
    added_by
    client_season
    metadata
  }
}

{
  "data": {
    "insert_api_points_one": {
      "id": 4,
      "amount": 10,
      "added_by": "729af390-29d0-402a-b73a-d2164d914020",
      "client_season": "my-campaign-name",
      "metadata": {
        "transaction_id": "tx_12345",
        "source": "twitter-engagement",
        "details": {
          "tweet_id": "1234567890",
          "action": "retweet",
          "timestamp": "2023-10-15T14:30:00Z"
        }
      }
    }
  }
}

mutation IssueOffChainPoints {
  insert_api_points_one(object: {
    account_id: "0xB58621209Dc0b0c514E52a6D9A165a16ae95e4f7", 
    identity_type: EVM_ADDRESS, 
    amount: "10", 
    reg_event_id: "ebffbc49-fa89-4e73-ab40-4e8be59331fd", 
    metadata: {
      transaction_id: "tx_12345",
      source: "twitter-engagement",
      details: {
        tweet_id: "1234567890",
        action: "retweet",
        timestamp: "2023-10-15T14:30:00Z"
      }
    }
  }) {
    id
    amount
    added_by
    client_season
    metadata
  }
}

{
  "data": {
    "insert_api_points_one": {
      "id": 4,
      "amount": 10,
      "added_by": "729af390-29d0-402a-b73a-d2164d914020",
      "client_season": "my-campaign-name",
      "metadata": {
        "transaction_id": "tx_12345",
        "source": "twitter-engagement",
        "details": {
          "tweet_id": "1234567890",
          "action": "retweet",
          "timestamp": "2023-10-15T14:30:00Z"
        }
      }
    }
  }
}

Before issuing points for an event, you must first register the event. This is a one-time process for each unique event. You can do this through the “API” sidebar at app.absinthe.network.

Absinthe’s off-chain points API allows any project the freedom to issue, query, update, and delete points for any off-chain action.

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, you can create your own via your season in the app.absinthe.network dashboard.

​
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

​
FAQ

​
Parameters

The client_season and added_by fields are visible via the gql queries but cannot be manually modified through mutations. The client_season field represents the name of your campaign and is used to organize and categorize point issuances.