Versions_ListMaterializationArtifacts
const url = 'https://dev-api.qualiastudios.dev/v1/accounts/example/datasets/example/versions/example/materializations/example/artifacts';const options = {method: 'GET', headers: {'X-API-Key': '<X-API-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://dev-api.qualiastudios.dev/v1/accounts/example/datasets/example/versions/example/materializations/example/artifacts \ --header 'X-API-Key: <X-API-Key>'A rendered dataset’s files in path order, each with a fresh signed URI. FAILED_PRECONDITION until the materialization has SUCCEEDED.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The account id.
The dataset id.
The version id.
The materialization id.
Query Parameters
Section titled “Query Parameters ”At most this many; 0 means 128, the maximum is 512.
From a previous response’s next_page_token. A token from before a new renderer took over is refused (FAILED_PRECONDITION): list again from the start.
Responses
Section titled “ Responses ”OK
Response for Versions.ListMaterializationArtifacts.
object
One page of files, in path order.
One file of a rendered dataset.
object
…/materializations/{materialization}/artifacts/{artifact}; {artifact} is its position in the listing, from 0.
Where it goes in the dataset’s directory, e.g. “meta/info.json”.
What it holds.
Its size in bytes.
Lowercase hex SHA-256 of its bytes, to check a download against.
Accounts/{account}/datasets/{dataset}/episodes/{episode}: the episode it was rendered from, when it holds one episode only.
The camera key, for a video.
Signed GET URI of its bytes; honours HTTP Range. Valid until expire_time.
When uri stops working; list again for a fresh one.
Empty on the last page.
Example
{ "materializationArtifacts": [ { "role": "ROLE_UNSPECIFIED" } ]}default
Section titled “default ”Default error response
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.
Example generated
{ "code": 1, "message": "example", "details": [ { "@type": "example" } ]}