Migrating from webhooks v2 to v3? Once you get your v3 subscription working, you will need to disable your v2 webhooks. Otherwise, you will continue to receive both v2 and v3 notifications (until webhooks v2 is eventually decommissioned).
To do this, please reach out to your Akamai Representative and we’ll be happy to disable v2 for you.
Now that you’ve created your webhooks subscription, make sure to test it out by taking actions you would expect to trigger a webhook notification to your receiver endpoint. Depending on your configuration, this could be:
If you need to modify the subscription you created, call the /webhooks/subscriptions/<subscriptionId>
endpoint with PATCH method.
This call requires the following header: Content-Type: application/merge-patch+json
Tips!
subscriptionId
to make this call (see the orange string in the below code). The subscriptionId
was returned in the response body when you created your webhooks subscription. You can also find it by listing your subscriptions.curl -X PATCH \
https://v1.api.REGION.janrain.com/CUSTOMER_ID/webhooks/subscriptions/subscriptionId \
-H 'Authorization: Bearer ACCESS_TOKEN' \
-H 'Content-Type: application/merge-patch+json' \
-d '{
"enabled": true,
"endpoint": "LISTENER_ENDPOINT",
"events": [WEBHOOK_EVENTS],
"title": "SUBSCRIPTION_TITLE"
}'
Response Status | Response Body | Outcome |
---|---|---|
200 OK |
Your subscription details | The call was successful and your subscription has been updated. |
With the Webhooks v3 APIs, you can fully service your webhooks subscriptions. See more information on how to:
You can also work with the webhooks events themselves. See: