Create or update artifacts

Create or update one or more artifacts

Only key and value are required to create an artifact. To update an artifact, its current version value must be provided.

In the following example body payload, one and two are existing artifacts, and three is new:

[
  { "key": "one", "value": "[ \"updating\", \"existing\", \"one\" ]", "version": 10, "content_type": "application/json" },
  { "key": "two", "value": "updating existing two", "version": 20 },
  { "key": "three", "value": "creating new three" },
]

Notes for this body:

• The value for key one is a JSON payload, so a content_type override is needed. This override must be done every time a JSON value is set.
• The version values for one and two mean they have been saved 10 and 20 times, respectively.
• If version is not provided for an existing artifact, the entire request will be refused and a Bad Request response will be sent.
• If version is provided for an artifact, it is only used for helping to prevent inadvertent data overwrites. It cannot be used to set the version of an artifact. The Looker server controls version.
• We suggest encoding binary values as base64. Because the MIME content type for base64 is detected as plain text, also provide content_type to correctly indicate the value's type for retrieval and client-side processing.

Because artifacts are stored encrypted, the same value can be written multiple times (provided the correct version number is used). Looker does not examine any values stored in the artifact store, and only decrypts when sending artifacts back in an API response.

Note: The artifact storage API can only be used by Looker-built extensions.

Request

Response