Describe the asset types

GET

/assets/delivery/v1/contracts

const url = 'https://api.ebitex.io/assets/delivery/v1/contracts';
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/contracts \
  --header 'Authorization: Bearer <token>'

Returns the three content types assets are described by: ebitex-image, ebitex-video and ebitex-document. Each lists its fields, and the file field carries the JSON Schema of the file object an asset of that type holds.

Fields an organization has added to a kind and marked as delivered follow the standard ones, so the list is the organization’s own: each is described with its type, whether it is required, and its settings. Internal fields are never listed.

The Content integration reads this to register the types. Call it directly to learn the exact shape of a file before you parse one.

Key: an Assets channel key (assets.delivery.read), minted for one channel in Assets. What it can see is that channel’s.

Authorizations

apiKey

Responses

200

{ "contracts": [{ "externalId": "ebitex-image", "name": "Image", "fields": [] }] }

401

missing_api_key or invalid_api_key: no key was sent, or it is unknown, revoked or expired, or its channel no longer exists.

402

payment_required: the organization’s subscription needs attention.

403

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.

429

too_many_failed_authentications: too many bad keys from this address; Retry-After says how long to wait.