Add a container image
Resolve the reference to a digest, track the image, and start the first scan unless scan is false. When the image is already tracked, Strix returns it with created false and a 200 status. Session callers must hold the admin or analyst role. Container scanning requires the Enterprise plan.
Authorizations
API token obtained from the Tokens endpoint or CLI device login. Include as Authorization: Bearer <token>. Requests made with a managed CLI session also include X-Strix-Workspace: <organization_id> to pin a process to the workspace it started in; recovery endpoints report the current workspace after a concurrent switch.
Body
Image reference in the form name:tag or name@sha256:<digest>.
Registry that hosts the image. Null uses the public Docker Hub.
OCI platform to add, for example linux/amd64. Null selects linux/amd64. A later scan of the image uses this platform if the scan request does not specify a platform.
Repository that builds this image. Strix shows the link on the image and uses it for remediation context.
Tag pattern to watch, for example 1.* or release-*. When set, Strix rescans the image when a matching tag moves to a new digest.
Start the first scan when the image is added. Default false.
Response
The image was already tracked.
A tracked container image with counts from its latest completed scan.
False when the image was already tracked.
Reason the first scan did not start. Null when scan is set or the caller disabled the scan.