Assets

Fetch list of assets provided by the Extension.

Assets

GET https://example-extension.mic.io/lvis/:lvis_instance_id/projects/:project_id/assets

Assets serve as a configuration mechanism that allows the Extension to expose specific key-value parameters to client applications. This channel is typically used to dynamically configure client-side libraries with service endpoints, environment-specific variables, or feature flags (e.g., read_endpoint, write_endpoint).

While the platform transmits this payload as a passthrough, strictly adhering to the name-data convention is required to ensure interoperability with client-side SDKs. The response must be a JSON array of objects, where each object represents a single configuration item containing a unique identifier and its associated value.

Asset schema:

• name (string): The key identifier for the configuration parameter.

• data (mixed): The value associated with the key (typically a string, boolean, or number).

Path Parameters

Name	Type	Description
lvis_instance_id	string	Unique identifier across all M/IC instances, in UUID format.
project_id	string	Project UUID.

200

[
  {
    "name": "read_endpoint",
    "data": "https://example-service.lvis.io"
  },
  {
    "name": "write_endpoint",
    "data": "https://example-service.lvis.io"
  },
  {
    "name": "use_base64",
    "data": true
  }
]

Example

cURL

curl --request GET \
  --url https://example-extension.mic.io/lvis/c068dd33-46c3-4789-a619-b14e4bcbe990/projects/da34516f-00af-435e-bd03-ab1720755dda/assets \
  --header 'Content-Type: application/vnd.api+json'

Response