Ethena Webhooks API
Webhooks are not enabled by default, please work with your sales representative to have them enabled if you need them.Once you have access, webhooks can be managed through the API. Currently, only the following webhooks are supported: - Learner Training Campaign Completed# SecurityRequests to the webhook URL include a header `X-Signature`, which contains a signature of the payload. This signature is generated using the secret key provided when the webhook was created.## Signature Verification To verify the signature of incoming requests, you need the secret key for a webhook. This key can be retrieved by calling `GET /v1/webhooks/{id}` after webhook creation. The secret key is not returned in the create webhook response. This key is used to generate a signature of the payload and compare it with the `X-Signature` header in the request.The signature is generated using the **HMAC SHA-256** algorithm. The **secret key** is used as the key, and the **request payload** is used as the data. The resulting HMAC is then converted into a hexadecimal string.For example:```jsconst crypto = require('crypto');const signature = crypto .createHmac('sha256', secretKey) .update(JSON.stringify(payload)) .digest('hex');```In this example:1. `secretKey` is the secret key that can be retrieved by calling `GET /v1/webhooks/{id}` after webhook creation.1. `payload` is the data you receive in the webhook request (usually in JSON format).1. The `crypto.createHmac()` function creates a hash object, which uses the SHA-256 algorithm and the `secretKey` as the key.1. `update()` adds the stringified payload to the hash.1. `digest('hex')` generates the HMAC hash in hexadecimal format, which can be compared to the `X-Signature` header in the request.# Retry PolicyWebhook requests will be attempted up to **three times**, with a retry interval of **five minutes**, before being considered failed.A **30-second request timeout** is enforced, meaning the webhook request must complete within 30 seconds. If the request exceeds this timeout, the attempt will be considered failed.
Ethena Webhooks API is one of 5 APIs that Ethena publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.
Tagged areas include Webhooks. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, authentication docs, a changelog, and an AsyncAPI specification.
This API exposes 6 operations across 3 paths. It is described by OpenAPI 3.1.0, at version 1.3.0.
Requests are made against a single base URL, https://api.goethena.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Ethena Webhooks API declares
1 security scheme
for authenticating requests.
It accepts HTTP basic authentication (basic_auth).
basic_auth— Send requests with the Authorization header that contains the word Basic followed by a space and a base64-encoded string of the username and api key, username:…
Paths & Operations 6
Across 3 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.
Webhooks are not enabled by default, please work with your sales representative to have them enabled if you need them. Once you have access, webhooks can be managed through the AP…
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Ethena 4
Other APIs Ethena publishes across the network.