Get the delivered schema bundle

GET

/content/delivery/v1/schemas

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

One JSON Schema (draft 2020-12) document describing what delivery returns for every contract published in the key’s environment, keyed {contractId}@{version} under $defs. It describes the published shape, not the one being edited, and $refs only resolve inside the same document.

content-sdk-codegen from @ebitex/content-sdk turns it into TypeScript types for your own content model. The bundle describes server-resolved responses, as a request with ctx gets them.

Key: a delivery key (content.delivery.read).

Authorizations

apiKey

Responses

200

401

missing_api_key or invalid_api_key: no key was sent, or it is unknown, revoked or expired.

403

scope_denied: the key lacks this route’s scope. origin_denied or ip_denied: a browser-safe key was used from an origin or address outside its restrictions. app_not_available: Content is not enabled for the organization.

429

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