List the custom field schema
GET /v1/custom-fields
The workspace’s custom field definitions - the keys accepted by the
customFields object on a contact, and what each one means. Read this once
at the start of an import so you write values under keys the CRM already
renders. Requires scope contacts:read.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Header Parameters
Section titled “Header Parameters ”Act on this workspace’s shared CRM pool. Membership is verified on every request, so an id you do not belong to falls back to personal scope rather than widening access. Omit it to use your default workspace. Applies to every CRM endpoint, not only the ones that list it here.
Responses
Section titled “ Responses ”Custom field definitions.
object
One user-defined field. The definition lives here, the value on the contact.
object
The key to use inside a contact’s customFields object.
JSON array of option strings
Missing or invalid bearer token.
Standard error envelope for all v1 error responses.
object
Machine-readable error code.
Human-readable explanation of the error.
Optional structured context (field-level validation errors, etc.).
Example
{ "error": "unauthorized", "message": "Invalid bearer principal"}The API key does not have the required scope for this operation.
Standard error envelope for all v1 error responses.
object
Machine-readable error code.
Human-readable explanation of the error.
Optional structured context (field-level validation errors, etc.).
Example
{ "error": "forbidden", "message": "scope contacts:write is required"}