Activate a rail for the caller's tenant
Until a rail is active for a tenant the Courier carries none of its inbound traffic: the Pix ingress resolves no tenant and the SPB drain reads nothing from the vendor. Engine sends, queries and mailbox reads pass regardless; to stop an engine’s sends, disable the engine, which also stops its deliveries. Activating spb starts the drain of the vendor queue, whose read is destructive: from then on the Courier, not the engines, consumes it. The tenant is the caller’s, the validated identity’s in multi-tenant and local in single-tenant, and is returned as tenantId — the identifier an engine’s credential path names. The first activation records the operator as registeredBy; every activation that changes the state, first or resume, records it as activatedBy and in the rail’s history. Activating a suspended rail resumes it; an active one is returned unchanged and records nothing. A single-tenant Courier carries one tenant per rail: activating a rail another tenant holds active is refused 409 JDC-0117. Needs the admin grant (channels activation:write); channels write is not enough.
Autorizações
JWT bearer token issued by the identity provider.
Cabeçalhos
Idempotency key; a retry with the same key replays the first answer.
Parâmetros de caminho
The rail. Closed vocabulary — a value outside it is a 404, never a new rail.
spb, pix Resposta
OK
spb, pix The operator who first activated the rail for the tenant.
128Only an ACTIVE rail carries the tenant's inbound traffic.
REGISTERED, ACTIVE, SUSPENDED The caller's tenant: the validated identity's in multi-tenant, local in single-tenant. The identifier an engine's credential path names.
255When the rail last began carrying inbound traffic.
The operator who last activated or resumed the rail. Absent on an activation that predates the rail audit.
128512The operator who suspended the rail. Absent when not suspended, or suspended before the rail audit.
128
