topic Re: Enable Secret Http in Custom Problem Notification in Alerting

Enable Secret Http in Custom Problem Notification

nakb — Mon, 04 Oct 2021 09:39:36 GMT

Hi,

I am trying to create a new problem notification using the API, but there is no option to toggle Secret Http Header Value, does anyone have idea how to achieve this.

Re: Enable Secret Http in Custom Problem Notification

ChadTurner — Fri, 29 Oct 2021 18:59:39 GMT

You are exactly right, from the API there is no designator to enable if this is a secret http value or not. It can only be done in the UI as of today. I would recommend tossing in a RFE so they can build that in to the API.

Test Results off:

ON:

I wonder if you just need to pass the value encoded for it to work, but i'd have to leave that to be confirmed from a Dev person.

Re: Enable Secret Http in Custom Problem Notification

nakb — Mon, 15 Nov 2021 06:35:28 GMT

Thanks Chad for the confirmation.

Re: Enable Secret Http in Custom Problem Notification

dirk_wall — Tue, 19 Apr 2022 19:16:55 GMT

Hi @nakb, @ChadTurner,

If you use the settings API (POST /api/v2/settings/objects) instead of the problem notifications API, you can create secret HTTP header values through the API. We're in the process of figuring out how to communicate this to the broader audience. Here is an example payload:

After the POST call, you can't read the secret values in the UI (duh), but if you try it out, e.g. with webhook.site, you'll see that this works just fine.

Hope this helps,

Cheers,

Dirk

Re: Enable Secret Http in Custom Problem Notification

adambrown12321 — Thu, 09 May 2024 10:27:52 GMT

This is a good answer, would be good to have this somewhere in the API docs! Unless I just couldn't find it there that is...