Pipeline entries

Move an entry

Changed on

Move an entry to another stage of its pipeline. laneId is the target stage's id from the pipeline's lanes; an id that does not exist on the entry's pipeline is ignored rather than errored. Omit lexorank to place the entry at the end of the target stage — it is the board position rank and only needs to be sent for an exact drag-and-drop position. Moving to a new stage runs the pipeline automations configured for that stage.

put/pipeline-entries/{entryId}/move

Request

  • Base URL
    https://api.gleap.io/v3
  • URL
    https://api.gleap.io/v3/pipeline-entries/{entryId}/move
  • Auth
    HTTP bearer

Path parameters

entryIdstring required

Headers

projectstring required

Request body

laneIdstring

Target stage — a lane id from the pipeline's lanes.

lexorankstring

Board position rank. Omit to place the entry at the end of the target stage.

Response

Ok

updatedAtstring required
createdAtstring required
laneChangedAtstring date-time
laneIdstring
dueDatestring date-time
lexorankstring
recordType'COMPANY' | 'CONTACT' required

What a pipeline holds. Persisted values — never rename a member, only add.

valuesunknown required
recordOwnerstring
recordValuesRecordStringAny

Construct a type with a set of properties K of type T

_idstring required

Changes

  • 276c488f9886Revision changes
    • info

      added the optional property / to the response with the status

  • 490b7d6391f3Revision changes
    • info

      added subschema #2 subschema #4 to the response body allOf list for the response status

    • info

      removed subschema #2 from the response body allOf list for the response status