⚙️ Public API
These API endpoints allow anyone to interact with the Hermes Protocol platform in a decentralized way. Through these, developers can create notifications for their users using their own dApp, increasing UX without compromising on user's privacy.
Base URL
https://api.hermesprotocol.io/api/public
Endpoints
POST /verify-user - See if a certain wallet address is registered on the platform.
POST /generate-bytes - Request a nonce to use in decentralized yet authenticated user requests.
POST /notification - Create a notification so that users are alerted
User Interaction flow
Supported Notifications
These are the supported notifications that you can create using the Hermes Protocol Public API.
For an exhaustive list, please find all created IDs here.
Notifications
Liquid Staking (Backbone Labs / Gravedigger)
NotificationTypeId | ChainId | CategoryId | ProjectId |
---|---|---|---|
002_0029 | zb1_002 | zb3_0008 | zb2_0034 |
Notification Parameters
contract
terra1l2nd99yze5fszmhl5svyh5fky9wm4nz4etlgnztfu4e8809gd52q04n3ea
tokenContract
terra17aj4ty4sz4yhgm08na8drc0v03v2jwr3waxcqrwhajj729zhl7zqnpc0ml
stakes / queueUnbond / submitBatch / finishUnbond
Param | Type | Description |
---|---|---|
flag | boolean | Whether the user wishes to receive alerts about this event or not |
value | number | Value to compare with the event |
type | comparison | Type of comparison used between the value configured and the value on the event |
Example
{
"stakes": {
"flag": true,
"value": 10,
"type": "="
},
"queueUnbond": {
"flag": true,
"value": 25,
"type": "<"
},
"submitBatch": {
"flag": true,
"value": 12,
"type": "<="
},
"finishUnbond": {
"flag": true,
"value": 100,
"type": ">"
}
}
scope
zc5_0001