Register an engine
Adding an engine is a configuration operation, not a software delivery. credentialSubject is the engine’s first credential; bind one per further calling product with bindEngineCredentialSubject. A credential subject binds at most one engine. Admin only (engines credential-subjects:write): a bound credential acts as the engine.
Autorizações
JWT bearer token issued by the identity provider.
Cabeçalhos
Idempotency key; a retry with the same key and body replays the first answer.
Corpo
The engine's first Access Manager credential subject; bind more with POST /v1/engines/{engineId}/credential-subjects. A subject binds at most one engine, disabled ones included.
1 - 256^[a-z0-9-]{1,32}$128The direct-participant ISPBs this engine acts as. Omitted or empty is legal, and an ISPB another engine already declares is accepted: a shared ISPB across two cores is the coexistence case itself.
^[0-9]{8}$Where the Courier delivers the Pix messages the ownership map gives this engine; https in production, and setting it needs the admin grant (engines pix-delivery:write). Omitted: the engine takes none, and such a message is retained.
Where the Courier relays the cross-core TED the ownership map gives this engine; https in production, and setting it needs the admin grant (engines ted-delivery:write). Omitted: the engine takes none, and a relay to it is refused.
Resposta
Created
Every Access Manager credential subject that authenticates as this engine, one per calling product, sorted.
256128^[a-z0-9-]{1,32}$^[0-9]{8}$
