Entity type. Non-artifact examples: gitCommit, languageModel (non-artifact ids use charset [-_.A-Za-z0-9]). Reserved artifact-backed types: artifact, package-version, application-version, release-bundle-version, build-version.

Entity identifier. May span multiple URL path segments.
Format depends on type:

Non-artifact types (e.g. gitCommit, languageModel):
typically a single segment. Allowed characters: [-_.A-Za-z0-9].

artifact — repo-relative path to the file, including nested folders and
the file name. Repository key is not part of id (pass it as ?repo=).
Lead subject = {repo}/{id}.

• Examples: file.txt, com/acme/service/1.2.3/service-1.2.3.jar
• Rejected: leading /, trailing /, empty segments (//), . or .. segments

package-version — {name}/versions/{version}. Split on the last
literal /versions/. Package type comes from ?repo= (repo config), not from
the id. {name} shape matches Artifactory leadFile for that package family:

• Maven: groupId:artifactId — org.apache.tomcat:catalina/versions/9.0.0
• npm (incl. scope): @myorg/widget/versions/2.0.1
• Docker/OCI: library/nginx/versions/1.27.0
• Go: github.com/acme/mod/versions/v1.2.3
• RPM: httpd/versions/2.4.51-1.el8
• Terraform module: hashicorp/consul/aws/versions/0.11.0
• PyPI / NuGet / Helm / Debian / Gems / Cargo / etc.: {pkgName}/versions/{version}
  URL-encode : and @ as needed; / remains path structure.

application-version — exactly two segments: {applicationKey}/{version}.
Neither segment may contain /. Example: orders-app/2.4.0.
Lead: {project-}application-versions/{applicationKey}/{version}/release-bundle.json.evd.

release-bundle-version — exactly two segments: {bundleName}/{version}.
Neither segment may contain /. Example: my-release/1.0.0.
Lead: {project-}release-bundles-v2/{bundleName}/{version}/release-bundle.json.evd.

build-version — two or three segments:
{buildName}/{buildNumber} or {buildName}/{buildNumber}/{buildTimestamp}.
buildName / buildNumber must not contain /. Optional buildTimestamp is
digits only (≤ 64). Omitting timestamp resolves to the latest matching build-info
file at request time. Examples: commons-build/1.0.0,
commons-build/1.0.0/1712345678901.

Artifactory repository key. Mutually exclusive with project and application. Non-artifact entities: explicit entity repository override (default {type}-entity). artifact / package-version: required — Artifactory repo of the lead artifact or package. Rejected for build-version, release-bundle-version, application-version.

Project key. Mutually exclusive with repo and application. Non-artifact entities: derives {project}-{type}-entity. build-version / release-bundle-version / application-version: selects project-qualified system repo (omit or default → default project). Rejected for artifact / package-version.

Application key. Mutually exclusive with repo and project. Non-artifact entities only: derives {application}-{type}-entity. Rejected for all reserved artifact-backed types.

Evidence provider identifier

Base64-encoded serialized in-toto Statement. Decoded shape for an
artifact subject:

{
  "_type": "https://in-toto.io/Statement/v1",
  "subject": [
    {
      "name": "example-binary",
      "digest": { "sha256": "4529c29..." }
    }
  ],
  "predicateType": "https://slsa.dev/provenance/v0.2",
  "predicate": { "...": "..." },
  "createdAt": "2026-02-09T11:45:00Z",
  "createdBy": "github-actions-bot",
  "markdown": "### Build Success\nThe binary was compiled using Go 1.22.",
  "attachments": [
    { "name": "build-log.txt", "sha256": "e3b0c44..." }
  ]
}

For an non-artifact entity (POST /entity/{type}/{id} with a non-reserved
type), the subject digest key must be the entity type (for example
gitCommit) rather than sha256:

{
  "_type": "https://in-toto.io/Statement/v1",
  "subject": [
    {
      "name": "57bb812f3733b80e270272ba063274e52c34bd23",
      "digest": { "gitCommit": "57bb812f3733b80e270272ba063274e52c34bd23" }
    }
  ],
  "predicateType": "https://slsa.dev/provenance/v0.2",
  "predicate": { "...": "..." },
  "createdAt": "2026-02-09T11:45:00Z",
  "createdBy": "github-actions-bot"
}

For artifact-backed reserved entity types (artifact, package-version,
application-version, release-bundle-version, build-version), the subject
digest is { "sha256": "<lead-file-checksum>" } — the same as evidence created
on the resolved lead artifact via the subject API.

The attachments field inside the Statement is optional and is part
of the signed payload (the signer commits to exactly that set).

Media type of the DSSE payload (must be application/vnd.in-toto+json).

The same endpoint also accepts two other body shapes (auto-detected by
the service - do not send a DSSE envelope if you use these):

• Sigstore Bundle - top-level mediaType with prefix
  application/vnd.dev.sigstore.bundle (e.g.
  application/vnd.dev.sigstore.bundle.v0.3+json); the bundle embeds
  its own DSSE envelope.
• OCI Evidence Bundle - top-level type: "oci.bundle"; the bundle
  embeds a DSSE envelope plus a public key.