Force Reindex

Triggers a reindex of specified artifacts and/or builds. Use this to reindex existing resources that may have missing component data. The total number of entities (artifacts + builds) cannot exceed the configured maximum (default 1000).

For some package types, dependency information lives in a separate package metadata file rather than the artifact binary itself. To recover that information you must force-reindex the metadata file, not just the artifact. Examples:

  • Docker: manifest.json (the manifest is the indexable entity for a Docker image; force-reindex also clears existing layer impact paths so they are re-derived from the manifest)

  • Maven: pom.xml

  • npm: package.json

  • Conan: conanfile.py

For artifacts whose dependencies are encoded in a separate metadata file, point path at the metadata file (see the "Reindex Docker manifest" example below).

Requires Admin permission.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Specifies which artifacts and/or builds to reindex. Provide at least one artifact or build. See the request-body examples (jarAndBuild, dockerManifest, mavenPom) for full payload shapes.

string

Optional Artifactory instance ID. Use default for the configured instance, or omit to let Xray resolve it automatically.

artifacts
array of objects

List of artifacts to reindex. For Docker, point path at the image's manifest.json; for Maven, point at the pom.xml; for binary artifacts (e.g. JARs), point at the artifact file.

artifacts
builds
array of objects

List of builds to reindex.

builds
boolean

If true, allows reindexing artifacts from non-indexed repositories.

Responses

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json