AgentEvals1

AI content12

AiModels1

Code1

Company10

ContactMemory6

Custom components5

Engagement7

Engagement Banner5

Engagement Chat Message5

Engagement Checklist5

Engagement Cobrowse5

Engagement Editor1

Engagement Email6

Engagement Modal5

Engagement News5

Engagement Product Tour5

Engagement Push Notification5

Engagement Survey10

Engagement Tooltip5

Engagement Whatsapp Messages6

FrontendTools1

Help center3

Help center articles15

Help center collections9

Help center redirects4

Invitation8

Knowledge3

Message templates6

Messages9

Pipeline entries6

Pipelines5

Project3

Records5

S2S Contacts6

S2S Conversations14

S2S Messages2

S2S Stream3

S2S Webhooks3

S2S Workflows1

Session24

Statistics9

Team5

Ticket48

Translations3

Uploads2

User11

Pipelines

List pipeline fields

The fields of one pipeline, in column order. A field's source says where its value lives: ENTRY fields are stored on the entry — their fieldIds are the keys entry values accept — while RECORD fields read (and write through to) an attribute of the company or contact and arrive on entries as recordValues. type, unit and calculation say how to render a value and what the stage footers total.

get/pipelines/{pipelineId}/properties

Path parameters

pipelineIdstring required

Headers

projectstring required

Response

propertyIdstring required

fieldIdstring required

labelstring required

What a property stores. The values are the persisted DB strings and are mirrored by the dashboard's PropertyType — never rename a member, only add.

Its own decorator-free module so pure services (and their harnesses) can import the enum without loading the Mongoose model.

source'ENTRY' | 'RECORD' required

Where a field's value lives.

ordernumber double required

widthnumber double

unitstring

calculation'sum' | 'average' | 'min' | 'max'

Footer totals the lane-stats aggregation supports. Numbers only.

recordPathstring

RECORD only: dotted path on the company/session document (value, customData.seats).

readOnlyboolean

RECORD only: the attribute cannot be written (e.g. last-seen device type).

Changes

Changed in 2 of the 22 revisions of this API.114

Sep 3, 2026490b7d6391f3113See the full diff
- ▲
  the response's property type changed from no type to object for status
  response-property-type-changed
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  removed subschema #1 subschema #2 subschema #4 from the response property allOf list for the response status
  response-property-all-of-removed
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 12, 2026fe2dff9fb04b1See the full diff
- ○
  endpoint added
  endpoint-added

Full history