Declare a deployment notification provider (inert until tested)

The provider is created DECLARED and delivers nothing. Activation
requires a passing connectivity probe measured against this exact configuration —
there is no field on this request that can skip that, because the database refuses
an ACTIVE row whose verdict was measured against different configuration.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Declare a notification provider, or replace an existing one's configuration.

config
required
int32
0 to 7

Where this mechanism sits in the scope's delivery chain: 0 is the primary, 1 the first fallback, and so on.

On a declare, an absent value means 0 — there is no prior position to preserve. On a replace, an absent value leaves the position unchanged; it is never defaulted to 0, because doing so would silently promote every edited provider to primary.

A value supplied on a replace is applied with insertion + renumber semantics: the provider is inserted at that index of the scope's chain for this channel and the remaining providers keep their relative order, renumbered contiguously from 0 in one transaction. A value deeper than the chain places the provider last.

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json