Get a folder's allowed contracts
const url = 'https://api.ebitex.io/content/management/v1/folders/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/allowed-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/content/management/v1/folders/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/allowed-contracts \ --header 'Authorization: Bearer <token>'The contracts declared directly on this folder as the only ones its components may use. An empty list means this folder declares nothing and inherits from the nearest folder above that does; effectiveAllowedContractIds on the folder listing gives the resolved answer.
A component satisfies the constraint when its contract is one of those listed or inherits from one. The constraint is checked when a component is created in or moved into the folder; components already there are not rechecked, and report conformsToFolderConstraint.
Needs the key’s role to hold content.access.manage.
Key: a management key with content.management.read.
Authorizations
Section titled “Authorizations”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters”Responses
Section titled “ Responses ”[ { "contractId": "…" } ]
missing_api_key or invalid_api_key: no key was sent, or it is unknown, revoked or expired.
payment_required: the organization’s subscription needs attention.
permission_denied: the key’s role lacks content.access.manage.
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.
No folder has this id.
Rate limit or quota exceeded; Retry-After says how long to wait. too_many_failed_authentications: too many bad keys from this address.