Replace a deployment provider's configuration (clears its verdict)

The recorded verdict described the PREVIOUS configuration, so it is cleared and the
provider must be tested again before it can be activated. An edit that produces
byte-identical configuration keeps its verdict — the same rule stated precisely, not
a second rule.

A chainPosition in the body is applied with insertion + renumber

semantics: the provider moves to that index of this scope's chain for its channel
and the others keep their relative order, renumbered contiguously from 0 in one
transaction. An ABSENT chainPosition leaves the position unchanged —
it is never defaulted to 0, which would silently promote an edited provider to
primary.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required
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