Blind-provision a delivery provider for a tenant (platform)

Declares a provider on the TENANT's chain, on the operator's authority, without
reading the tenant's data.

The row is created DECLARED and is inert: it delivers

nothing until a connectivity test passes and it is enabled. That is the same rule
the tenant plane applies, because it is the same code — an unverified provider
never sends.

chainPosition is numeric, 0..7, and defaults to 0.

Position 0 is the primary; the rest are the failover sequence in order.

The ROOT platform tenant is not a valid target: its chain IS the deployment plane, reached at /api/v3/admin/platform/notification/providers.

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

The mechanism's configuration and its position in the tenant's chain.

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