List pipeline fields
Changed onThe 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.
Request
- Base URLhttps://api.gleap.io/v3
- URLhttps://api.gleap.io/v3/pipelines/{pipelineId}/properties
- AuthHTTP bearer
Path parameters
Headers
Response
Ok
Changes
- breaking
the
response's property type changed from no type toobjectfor status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status - info
removed
subschema #1subschema #2subschema #4from theresponse propertyallOflist for the response status - info
added the required property
/to the response with the status - info
added the required property
/to the response with the status - info
added the required property
/to the response with the status - info
added the required property
/to the response with the status - info
added the required property
/to the response with the status - info
added the required property
/to the response with the status
- breaking
- info
endpoint added
- info