List adapters

GET

/content/management/v1/adapters

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

Lists the adapters in the key’s environment, ordered by external id. An adapter is a named, reusable field mapping from an input contract to an output contract, with one rule per output field.

Each item carries usageCount: how many things use the adapter, counting presentation bindings, streams that project through it, and other adapters whose rules nest it. realmId names the realm that owns it; an adapter owned by a realm above the key’s own is read-only here.

Key: a management key with content.management.read.

Authorizations

apiKey

Responses

200

An array of { id, externalId, name, inputContractId, outputContractId, realmId, usageCount }.

401

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

402

payment_required: the organization’s subscription needs attention.

403

scope_denied: the key lacks this route’s scope. tier_required: the Content Management API needs the Pro plan or above. ip_denied: the caller’s address is outside the key’s allowed ranges. app_not_available: Content is not enabled for the organization.

429

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