Check a configuration for this tenant without persisting it

Persists nothing and contacts nothing. It answers whether the configuration would be
ACCEPTED — shape, required fields, and the mechanism's own pre-contact rules,
including the SSRF classification of an operator-supplied relay host and the refusal
of plaintext submission to a routable one. The same rules run on the write path, so
an accepted answer here is the answer POST will give.

The attempt IS audited, through an independent transaction, because the fact that an operator submitted a configuration for checking is worth keeping even when the answer is no.

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.

Responses
204

The configuration would be accepted

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