List field types

GET

/content/management/v1/field-types

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

Lists the field types a contract field can use in this organization, including any a plugin contributes. Each has a key (the fieldTypeKey a field names), a displayName, the JSON Schema its settings must match (settingsSchema), and isDeprecated.

A deprecated type still works for existing fields but should not be chosen for new ones. Read this list rather than hard-coding field types or their settings: it is the authoritative description of what a field can hold.

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

Authorizations

apiKey

Responses

200

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.