> ## Documentation Index > Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL. > Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other. > Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking. > Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify. # Generates the signedUrl for accessing the resource > GET /api/v1/artifacts/id/{id}/url. Storage API reference. Sign in to try this endpointExplore the parameters, examples, and responses below. Connect your ZedCloud session when you’re ready to send a request. > [accordion] Connect your console > > Sign in to your usual ZedCloud console, then open: > >
    >
  1. Profile menu
  2. Help & Documentation
  3. API Reference
    4. >
> > Your cluster and authorization are filled in automatically. No token to copy. > [More about signing in ](https://zededa.mintlify.site/api-reference/authentication.md#sign-in-to-the-api-reference) Modifying requests stay off until you enable them. [Authentication](https://zededa.mintlify.site/api-reference/authentication.md) · [API availability](https://zededa.mintlify.site/api-reference/clusters.md) · [Download OpenAPI](https://zededa.mintlify.site/openapi/services/storage.json) A successful response. Temporary Redirect. Returned when the requested artifactId is not available at the requested time Bad Request. The API gateway did not process the request because of invalid value of parameters. Unauthorized. The API gateway did not process the request because it lacks valid authentication credentials for the target resource. The request header has either no authorization details or an authorization that has been refused. Forbidden. The API gateway did not process the request because the requestor does not have edge-node level access permission for the operation or does not have access scope to the project. Internal Server Error. The API gateway experienced an unexpected condition. Specific error condition is indicated in error codes. Gateway Timeout. The API gateway did not receive a timely response from an upstream microservice it needed to communicate with in order to complete the request. An unexpected error response. ## OpenAPI ````yaml openapi/services/storage.json GET /v1/artifacts/id/{id}/url openapi: 3.0.0 info: title: ZEDEDA Storage Service description: >- The ZEDEDA Storage Service is helper service to ZEDEDA Edge Application Service. This service allows customers to store edge application images and other artifacts (e.g. logo, screenshot, license, developer agreement etc.) in Datastores. This service allows customers to select datastores -- ZEDEDA owned and operated Datastores in public cloud (AWS S3 or Azure Blobstorage) -- Public Datastores (e.g. Docker Hub, Azure Container registry etc.) -- Customer owned and operated Datastores in public cloud (AWS S3 or Azure Blobstorage) -- Customer owned and operated Datastores in their own enterprise Data Centre This service allows binary files of the images and artifacts to be uploaded in one of the above Datastores, artifacts to be downloaded from datastores. Edge nodes will download edge application image binary files from these datastores termsOfService: https://www.zededa.com/terms version: '1.0' contact: name: ZEDEDA API Support url: https://www.zededa.com/support email: support@zededa.com license: name: Apache 2.0 url: http://www.apache.org/licenses/LICENSE-2.0.html servers: - url: https://{apiHost}/api variables: apiHost: default: invalid.invalid description: Connect from ZedUI to supply your verified API destination. security: - BearerToken: [] tags: - name: ImageConfiguration - name: DatastoreConfiguration - name: ArtifactManager - name: VolumeInstanceConfiguration - name: VolumeInstanceStatus externalDocs: description: ZEDEDA Product Documentation url: https://docs.zededa.com/-M-8m8d8KqdLpfOgY_jo/storage paths: /v1/artifacts/id/{id}/url: get: tags: - ArtifactManager summary: Generates the signedUrl for accessing the resource description: >- Generate the URL which can be used to access the resource from datastore like s3, Azure etc for specified amount of time. operationId: ArtifactManager_GetArtifactSignedUrl parameters: - name: id description: system generated unique id for an artifact in: path required: true schema: type: string - name: X-Request-Id in: header required: false description: User-Agent specified id to track a request schema: type: string responses: '200': description: A successful response. content: application/json: schema: $ref: '#/components/schemas/Artifact' '307': description: >- Temporary Redirect. Returned when the requested artifactId is not available at the requested time content: application/json: schema: $ref: '#/components/schemas/ZsrvResponse' '400': description: >- Bad Request. The API gateway did not process the request because of invalid value of parameters. content: application/json: schema: $ref: '#/components/schemas/ZsrvResponse' '401': description: >- Unauthorized. The API gateway did not process the request because it lacks valid authentication credentials for the target resource. The request header has either no authorization details or an authorization that has been refused. content: application/json: schema: $ref: '#/components/schemas/ZsrvResponse' '403': description: >- Forbidden. The API gateway did not process the request because the requestor does not have edge-node level access permission for the operation or does not have access scope to the project. content: application/json: schema: $ref: '#/components/schemas/ZsrvResponse' '500': description: >- Internal Server Error. The API gateway experienced an unexpected condition. Specific error condition is indicated in error codes. content: application/json: schema: $ref: '#/components/schemas/ZsrvResponse' '504': description: >- Gateway Timeout. The API gateway did not receive a timely response from an upstream microservice it needed to communicate with in order to complete the request. content: application/json: schema: $ref: '#/components/schemas/ZsrvResponse' default: description: An unexpected error response. content: application/json: schema: $ref: '#/components/schemas/googlerpcStatus' externalDocs: description: ZEDEDA Product Documentation url: https://docs.zededa.com/-M-8m8d8KqdLpfOgY_jo/storage components: schemas: Artifact: type: object properties: id: type: string description: system generated unique id for an artifact readOnly: true pattern: '[a-zA-Z0-9][a-zA-Z0-9_.-]+a' x-zededa-source-issues: - code: inapplicable-constraint pointer: '#/definitions/Artifact/properties/id' keyword: uniqueItems sourceValue: true name: type: string description: >- User defined name of the artifact, unique across the enterprise. Once object is created, name can’t be changed maxLength: 256 minLength: 3 pattern: '[a-zA-Z0-9][a-zA-Z0-9_.-]+' x-zededa-source-issues: - code: inapplicable-constraint pointer: '#/definitions/Artifact/properties/name' keyword: uniqueItems sourceValue: true status: description: describes the status of the operation readOnly: true allOf: - $ref: '#/components/schemas/Status' signedUrl: type: string description: generated signed url for an artifact readOnly: true ttl: type: number format: int64 description: TTL for the URL readOnly: true description: ArtifactKey idenfies the artifact by artifactId title: ArtifactKey detail ZsrvResponse: type: object properties: operationType: title: |- Describes one of the operations type : possible values Read/Delete/Create/Update/List allOf: - $ref: '#/components/schemas/ZcOpsType' operationStatus: title: if this is log running job allOf: - $ref: '#/components/schemas/ZcOpsStatus' objectKind: type: string title: zedcloud object kind on which the operation was performed objectId: type: string title: Unique value identifies the object that was operated on objectName: type: string title: name of the object objectRevision: type: string title: |- object revision post the operation, note Read operation doesn't change the revision objectType: $ref: '#/components/schemas/ObjectType' operationTime: type: string title: time of operation startTime: type: string title: total time taken by operations endTime: type: string user: type: string title: the operation is performed on behalf of this user httpStatusCode: type: integer format: int32 title: http response httpStatusMsg: type: string title: summary of the error in text format jobId: type: string title: for tracking asynchronous tasks error: type: array items: $ref: '#/components/schemas/ZsrvError' title: |- one or more errors will be set if the operation failed i.e. httpStatusCode != 2xx googlerpcStatus: type: object properties: code: type: integer format: int32 message: type: string details: type: array items: $ref: '#/components/schemas/protobufAny' Status: type: object properties: code: type: string description: >- describes the overall status of the operation **Source definition conflict:** this property declares default `"SUCCESS"`, but the referenced definition declares `"STATUS_CODE_UNSPECIFIED"`. No default is documented here pending correction in ZEDEDA's Swagger definition. readOnly: true allOf: - type: string enum: - STATUS_CODE_UNSPECIFIED - STATUS_CODE_SUCCESS - STATUS_CODE_FAILURE - STATUS_CODE_PARTIAL_SUCCESS title: status codes for internal use (Gilas and Niles) x-zededa-source-issues: - code: conflicting-reference pointer: '#/definitions/Status/properties/code' keyword: default sourceValue: SUCCESS reference: '#/definitions/StatusCode' referencedValue: STATUS_CODE_UNSPECIFIED description: description: top level description of the operation readOnly: true allOf: - $ref: '#/components/schemas/Description' description: Status encapsulates the top level status of the operation title: Status encapsulates the top level status of the operation ZcOpsType: type: string enum: - OPS_TYPE_UNSPECIFIED - OPS_TYPE_READ - OPS_TYPE_DELETE - OPS_TYPE_CREATE - OPS_TYPE_UPDATE - OPS_TYPE_LIST default: OPS_TYPE_UNSPECIFIED title: ZedCloud internal operation type ZcOpsStatus: type: string enum: - OPS_STATUS_UNSPECIFIED - OPS_STATUS_PENDING - OPS_STATUS_ONGOING - OPS_STATUS_COMPLETE default: OPS_STATUS_UNSPECIFIED description: >- - OPS_STATUS_PENDING: In rare cases, system may not start operation when it was requested. Client will be notified that operation is PENDING - OPS_STATUS_ONGOING: system will start the operation, but at the time response was generated, operation is still ONGOING. - OPS_STATUS_COMPLETE: Even if the result of the operations may result in failure, but the OpsStatus will marked COMPLETE for almost all cases. title: ZedCloud internal operation status ObjectType: type: string enum: - OBJECT_TYPE_UNSPECIFIED - OBJECT_TYPE_USER - OBJECT_TYPE_EDGE_NODE - OBJECT_TYPE_EDGE_APP - OBJECT_TYPE_IMAGE - OBJECT_TYPE_EDGE_APP_INSTANCE - OBJECT_TYPE_PROJECT - OBJECT_TYPE_NETWORK - OBJECT_TYPE_DATASTORE - OBJECT_TYPE_SERVICE - OBJECT_TYPE_SERVICE_INSTANCE - OBJECT_TYPE_ENTERPRISE - OBJECT_TYPE_ROLE - OBJECT_TYPE_CREDENTIAL - OBJECT_TYPE_NETWORK_INSTANCE - OBJECT_TYPE_VOLUME_INSTANCE - OBJECT_TYPE_REALM - OBJECT_TYPE_AUTHPROFILE - OBJECT_TYPE_POLICY - OBJECT_TYPE_APP_POLICY - OBJECT_TYPE_CLUSTER_INSTANCE - OBJECT_TYPE_PLUGIN - OBJECT_TYPE_DOC_POLICY - OBJECT_TYPE_ORCHESTRATOR_CLUSTER - OBJECT_TYPE_TAGS - OBJECT_TYPE_EDGE_NODE_INTERFACE - OBJECT_TYPE_DEPLOYMENT - OBJECT_TYPE_ENTITLEMENTS - OBJECT_TYPE_DATA_STREAM - OBJECT_TYPE_API_USAGE - OBJECT_TYPE_APP_INSTANCE_SNAPSHOT - OBJECT_TYPE_PATCH_ENVELOPE - OBJECT_TYPE_RESOURCE_USAGE_TRACK - OBJECT_TYPE_PATCH_ENVELOPE_REFERENCE - OBJECT_TYPE_DEV_PASSTHROUGH - OBJECT_TYPE_EDGE_NODE_CLUSTER - OBJECT_TYPE_ASSET_GROUP - OBJECT_TYPE_APP_PROFILE - OBJECT_TYPE_PROFILE_DEPLOYMENT - OBJECT_TYPE_ZKS_INSTANCE - OBJECT_TYPE_CLUSTER_GROUP default: OBJECT_TYPE_UNSPECIFIED ZsrvError: type: object properties: ec: title: |- Enumrated error code, describes more granular numerical value than just httpStatus allOf: - $ref: '#/components/schemas/ZsrvErrorCode' location: type: string title: 'Ignore: Internal field only' details: type: string title: Field captures string description of details protobufAny: type: object properties: typeUrl: type: string value: type: string format: byte Description: type: object properties: descMessage: type: string description: description of an operation readOnly: true descCode: type: string description: >- description code for an operation **Source definition conflict:** this property declares default `"UPLOAD_DONE"`, but the referenced definition declares `"DESCRIPTION_CODE_UNSPECIFIED"`. No default is documented here pending correction in ZEDEDA's Swagger definition. readOnly: true allOf: - type: string enum: - DESCRIPTION_CODE_UNSPECIFIED - DESCRIPTION_CODE_RECEIVED - DESCRIPTION_CODE_PACKET_CORRUPT - DESCRIPTION_CODE_FAILED_TO_RECEIVE - DESCRIPTION_CODE_NETWORK_ERROR - DESCRIPTION_CODE_NOT_FOUND - DESCRIPTION_CODE_NOT_SUPPORTED - DESCRIPTION_CODE_INTERNAL_ERROR - DESCRIPTION_CODE_NOT_SPECIFIED - DESCRIPTION_CODE_UPLOAD_DONE - DESCRIPTION_CODE_ALREADY_EXISTS - DESCRIPTION_CODE_INVALID_PARAMS title: description codes for internal use (Gilas and Niles) x-zededa-source-issues: - code: conflicting-reference pointer: '#/definitions/Description/properties/descCode' keyword: default sourceValue: UPLOAD_DONE reference: '#/definitions/DecsriptionCode' referencedValue: DESCRIPTION_CODE_UNSPECIFIED description: Description encapsulates the top level Description of the operation title: Description encapsulates the top level Description of the operation ZsrvErrorCode: type: string enum: - zMsgErrorNone - zMsgSucess - NotFound - AlreadyExists - VersionMismatch - RangeError - LargeResult - IncompleteData - InvalidData - FunctionUnsupported - NoMemory - SendFailure - Timeout - BadReqBody - BadReqParam - InvalidFieldFormat - UrlNotFound - ApiVersionNotSupported - Unauthorized - Forbidden - Conflict - NotModified - DependencyConflict - JsonFmtError - ProtoFmtError - CertError - DataBaseConnection - DBError - zMsgAccepted - zMsgCreated - PreConditionFailed - InternalServerError default: zMsgErrorNone description: |- - zMsgErrorNone: common validation errors - IncompleteData: message had fields that weren't filled in - InvalidData: message contained the field that wasn't expected - FunctionUnsupported: this feature unavailable on this version of device - InvalidFieldFormat: message contained the field that wasn't correctly formatted - JsonFmtError: Marshal / Unmarshal errors - DataBaseConnection: generic DB error title: ZedCould internal error code securitySchemes: BearerToken: type: http description: Bearer token for user session scheme: bearer ````