Check a configuration for a tenant without persisting it (platform)

Answers whether a configuration would be ACCEPTED, and records the attempt. It
persists nothing and contacts nothing — the pre-contact rules (internal or
unresolvable host, plaintext transport) are evaluated locally, so a refusal costs no
socket in either container.

Scoped .write rather than .test, matching both shipped

planes: .test exists because a test reaches OUT, and this reaches
nothing.

The attempt is audited either way. A refused check is the row worth having: it is the same action repeated while probing what the SSRF guard permits.

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