Internal endpoint for extension runners and deployment validation. It checks whether a supplied content hash belongs to the currently installed extension version for the supplied tenant and extension registry ID. The EE action uses an admin database connection, reads tenant_extension_install by tenant_id and registry_id, and checks extension_bundle for a matching version_id and content_hash. A negative validation result is returned as 200 with valid=false, not as 404. Requires x-api-key; the Express middleware allows the ALGA_AUTH_KEY runner secret or a valid database API key.
Query parameters
tenantstring <uuid>Required
Tenant UUID from tenant_extension_install.tenant_id.
extensionstring <uuid>Required
Extension registry UUID from tenant_extension_install.registry_id.
hashstringRequired
Bundle content hash to validate. The EE action accepts sha256:<64 hex chars> or a raw 64-character hex string and normalizes raw hex to sha256: form.
Header parameters
x-canarystringOptional
Optional runner canary identifier used only for logging and cache variance.