Deploy Artifact by Checksum

Deploy an artifact to the specified destination by checking if the artifact content already exists in Artifactory.

If Artifactory already contains a user-readable artifact with the same checksum, the artifact content is copied to the new location and returns a response without requiring content transfer.

Otherwise, a 404 error is returned to indicate that content upload is expected to deploy the artifact.

If the X-Checksum-Deploy header is set to false, the artifact will be uploaded successfully with a 201 response, even if it didn't exist before, and submitted checksums will have the status Uploaded: Identical.

You can also attach properties when deploying artifacts.

Since: 2.5.1

Security: Requires a user with Deploy permissions (can be anonymous)

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
length ≥ 1

Repository key

string
required
length ≥ 1

Path to the artifact within the repository

Body Params

Binary content of the artifact (not needed if artifact already exists in Artifactory)

Headers
boolean
enum
required

Must be set to true for checksum-based deployment

Allowed:
string

SHA1 checksum value. At least one checksum header (X-Checksum-Sha1, X-Checksum-Sha256, or X-Checksum) must be provided.

string

SHA256 checksum value. At least one checksum header (X-Checksum-Sha1, X-Checksum-Sha256, or X-Checksum) must be provided.

string

Generic checksum value (type resolved by length: 32 chars=MD5, 40 chars=SHA1, 64 chars=SHA256). At least one checksum header (X-Checksum-Sha1, X-Checksum-Sha256, or X-Checksum) must be provided.

string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
URL
LoadingLoading…
Response
Choose an example:
application/json
application/vnd.org.jfrog.artifactory.storage.ItemCreated+json