Declare that an engine is in bypass on this rail
Records that an engine was reconnected directly to the vendor. Activating the bypass itself is a configuration change in the engine; this operation declares the fact to the Courier so it suspends its guarantees explicitly instead of reporting green while blind. With one engine in bypass, declaring a second on the same (tenant, channel) returns 409 JDC-0301 — the database’s partial unique index decides it. Declaring the same engine again keeps the one active row: its declaredAt becomes the earlier of the two (the interval only ever lengthens) and its reason the new one. A backdated declaration overlapping another engine’s cleared bypass is accepted, and the Courier logs a WARN naming both engines and the overlap interval. A rail that declares no bypass refuses with 422 JDC-0501. While a bypass is active the Courier’s own SPB consumer takes nothing for that (tenant, channel).
Authorizations
JWT bearer token issued by the identity provider.
Headers
Idempotency key; a retry with the same key and body replays the first answer.
Path Parameters
The rail. Closed vocabulary — a value outside it is a 404, never a new rail.
spb, pix Body
^[a-z0-9-]{1,32}$Required — a bypass suspends coexistence guarantees.
1 - 512When the engine began talking to the vendor directly, if before now. A bypass activated while the Courier was unreachable is declared after the fact; any past instant down to the channel's registration for the tenant is accepted and recorded as given; a future one, the zero instant, or one before that registration is refused 422. Omitted means now. Reconciliation marks every cycle overlapping the interval from this instant.
Response
OK
spb, pix 128^[a-z0-9-]{1,32}$512Guarantees explicitly suspended while the bypass is active.
64
