Download a cache artifact
Downloads a cache artifact identified by its `hash` specified on the request path. The artifact is downloaded as an octet-stream (binary data). The artifact data is a gzip-compressed tarball containing the cached task outputs. The client will verify the content-length header against the response body size.
Authorization
bearerToken Bearer token authentication. Pass your authentication token in the Authorization header as Bearer <token>.
For self-hosted implementations, the token format and validation logic is up to the implementer. Common approaches include:
- Static tokens for simple setups
- JWT tokens for stateless authentication
- OAuth2 tokens for integration with identity providers
In: header
Path Parameters
The artifact hash. This is a content-addressable hash that uniquely identifies the cached artifact based on task inputs.
^[a-fA-F0-9]+$1 <= lengthQuery Parameters
The team identifier to perform the request on behalf of. Used for multi-tenant cache implementations where artifacts are scoped to teams.
The team slug to perform the request on behalf of. Alternative to teamId for identifying the team.
Header Parameters
The continuous integration or delivery environment where this artifact operation is being performed. Examples: github-actions, circleci, jenkins.
length <= 50Indicates whether the client is running in an interactive shell. 1 for interactive, 0 for non-interactive (CI/scripts).
0 | 1Response Body
application/octet-stream
application/json
application/json
application/json
application/json
curl -X GET "https://localhost:3000/artifacts/string""string"{
"code": "string",
"message": "string"
}{
"code": "string",
"message": "string"
}{
"code": "string",
"message": "string"
}{
"code": "string",
"message": "string"
}