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.
Encabezados
Parámetros de ruta
Respuesta
OK

