How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Goethena 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.

Goethena Webhooks API is one of 5 APIs that Goethena publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Webhook. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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.

6 operations 3 paths 0 schemas 1 DELETE2 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.3.0
Base URL
https://api.goethena.com
Authentication
HTTP Basic
Terms of Service
Resource Areas
1

Authentication & Security 1

Goethena 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 6

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…

GET
/v1/webhooks
Get webhooks
getWebhooks → 200400401403
POST
/v1/webhooks
Create a new webhook
createWebhook body → 200400401403
GET
/v1/webhooks/{id}
Get a webhook by id
getWebhookById 1 param → 200400401403404
PATCH
/v1/webhooks/{id}
Update webhook by id
patchWebhookById 1 param body → 204400401403404
DELETE
/v1/webhooks/{id}
Delete a webhook by id
deleteWebhookById 1 param → 204400401403404
POST
/v1/webhooks/{id}/trigger
Trigger a webhook by id
triggerWebhookById 1 param body → 204400401403404

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

goethena-webhooks-api-openapi.yml Raw ↑

Other APIs Goethena publishes across the network.

Goethena Learner Training Campaigns API
Goethena Learner Training Modules API
Goethena Learners API
Goethena Training Campaigns API
Where this information came from

This is an independent, third-party profile of Goethena Webhooks API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.