Update Engine Config
Replace an engine’s active configuration. The full config is validated before swap.
Authorizations
Send the credential as Authorization: Bearer <key>.
Scoped partner credentials use the exclusive nxsk_v1_... namespace.
Each scoped key is bound at issuance to one organization, one canonical
named environment, an explicit engine set, and a least-privilege
capability set. A malformed, unknown, rotated, or revoked nxsk_ key
fails closed and is never retried as a legacy key.
Capabilities used by this API are runs:write, runs:read,
engines:read, catalog:read, webhooks:manage,
runs:defensibility:read, runs:test, and converse:use. Operation
descriptions name the required capability.
Grandfathered nx_live_... and nx_test_... keys retain their existing
broad access during the compatibility window.
Path Parameters
Engine identifier slug (e.g. default).
Body
Full replacement config. Must conform to the engine's type-specific schema. Use the validate endpoint to check before saving.
Response
Config updated successfully.
Engine configuration with audit metadata. The config structure
varies by engine_type. The per-engine Contract page on
platform.usenexio.com is the canonical integration-guide surface
for your engine's typed request schema.
Engine configuration object. Structure depends on engine_type.
When the config was last updated, or null if never modified after creation.
API key identifier that last updated the config, or null.
Engine type.
placement, entity_analysis, diligence Default configuration template for this engine type.