Get an asset for one locale
const url = 'https://api.ebitex.io/assets/delivery/v1/assets/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/rendition';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
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://api.ebitex.io/assets/delivery/v1/assets/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/rendition \ --header 'Authorization: Bearer <token>'Returns the same asset as GET /assets/{id}, with every localized member already resolved to a plain value for locale: file is the one rendition, and alt and caption are strings.
locale is a code from the organization’s locale tree. The API falls back along that tree from the code you send, for example de-AT then de then the default rendition. It never matches by prefix. Without locale, or when the organization has no locales, you get the default.
An asset can be restricted to an audience. Send the visitor’s audience token in the X-Ebitex-Audiences header (the content SDK does this for you). Without a token that grants the audience the asset has no link at all: this read answers 403 with members_only and the asset’s kind, and nothing else about it. With one, the asset is returned with links that last five minutes and an expiresAt that says when they stop. A list shows a restricted asset the token does not grant as a stub: its name, its type, and "restricted": true, with no file and no thumbnail.
A channel decides what a key sees: its folders, its categories, and whether private assets are included. An asset outside the channel answers 404, exactly as one that does not exist, so a key can never read by id what it cannot list. Responses are never cached: links to private assets are minted for each response.
Key: an Assets channel key (assets.delivery.read), minted for one channel in Assets. What it can see is that channel’s.
Authorizations
Section titled “Authorizations”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters”Query Parameters
Section titled “Query Parameters”Responses
Section titled “ Responses ”OK
missing_api_key or invalid_api_key: no key was sent, or it is unknown, revoked or expired, or its channel no longer exists.
payment_required: the organization’s subscription needs attention.
members_only: the asset is restricted to an audience the visitor’s token does not grant. The body names the asset’s kind and nothing else.
scope_denied: the key lacks assets.delivery.read. app_not_available: Assets is not enabled for the organization. origin_denied or ip_denied: the key was used from an origin or address outside its restrictions.
not_found: there is no such asset, or it is outside the key’s channel.
too_many_failed_authentications: too many bad keys from this address; Retry-After says how long to wait.