List dangling references

GET

/content/management/v1/references/dangling

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

Lists every reference in the key’s environment whose target does not exist there: a component field or page that points at a component or page this environment lacks, typically because a promotion skipped it. Changes nothing.

Each item names the source (sourceKind, sourceId, sourceName, the fieldPath holding the reference, and its folder, contract or site path) and the missing targetKey. presentIn lists the environments that promote directly into this one and do hold the target. Promoting the target alone does not repair the reference: promote the source again once its target exists here.

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

Authorizations

apiKey

Responses

200

{ "items": [ … ] }; an empty list means nothing dangles.

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.