| ID | NFR-2006 |
|---|---|
| Name | Keelvar WebHook Registration and Orchestration |
| Author | Richard McArthur ( richard.mcarthur-ext@syensqo.com ) |
| Approver | Sascha Wenninger ( sascha.wenninger-ext@syensqo.com ) |
Purpose
Several single execute processes need to be processed before Keelvar is able to communicate effectively with SAP CI, because of the single execution nature of these calls (for registration) they are being considered as technical configuration but doesn't form part of official configuration documents as they are required only by the Syensqo integration build to facilitate integration.
Execution
Webhook registration
Sample Request
{
"url": "https://dev-api.syensqo.com/status",
"name": "AwardFeed",
"description": "All WebHook SCPI DEV",
"triggers": [
"AWARD_FEED_UPDATED","JOB_UPDATED","SOURCING_EVENTS_FEED_UPDATED"
],
"signing_alg": "HMAC_SHA256",
"signing_key": "tEnAvVNFx4YYTnAimo1ABwtfGNyndEM7yZwh8BZ4BrI="
}
Sample Response
{
"uuid": "e8309c18-4437-45d7-bc8c-0bbe137db54e",
"name": "AwardFeed",
"description": "All WebHook SCPI DEV",
"url": "https://dev-api.syensqo.com/status",
"triggers": [
"AWARD_FEED_UPDATED",
"JOB_UPDATED",
"SOURCING_EVENTS_FEED_UPDATED"
],
"signing_alg": "HMAC_SHA256",
"signing_key": "0006f99f3e831ae640596b119d85c3f097620c147296c8d2d2f1a022348ec621"
}
The Signing key and algorithum is then returned which should be used for each trigger of the webhook.