List pipelines and groups
GET
/backend/pipelinesResponse
Groups ordered by
positionPipelines ordered by
position, each with its group_idGet a pipeline
GET
/backend/pipelines/{id}The default stage names (
Entrada, Em andamento, Ganho, Perdido) and the default loss
reasons are created by the API in Portuguese and returned verbatim. They are editable data —
rename them with Configure a pipeline.color uses the design system token format — an HSL triple without the hsl() wrapper,
like "217 91% 60%".Create a pipeline
POST
/backend/pipelinespipeline.manage permission. The created pipeline already comes with the
four default stages and the default loss reasons.
Request Body
Pipeline name
Pipeline description
UUID of an existing group
Name of a group to create along with the pipeline
Configure a pipeline
PUT
/backend/pipelines/{id}Request Body
Pipeline name
Pipeline description
The complete and ordered list of stages. The position in the array defines the order on the board.
The complete list of the pipeline’s loss reasons
Map
{ "removed_stage_id": "destination_stage_id" } for the stages that left the listid).
Reorder a pipeline
PUT
/backend/pipelines/reorderRequest Body
UUID of the moved pipeline
UUID of the destination group
UUID of the pipeline that should end up after the moved one. Omit to place it at the end of the group.
Delete a pipeline
DELETE
/backend/pipelines/{id}Groups
Groups organize pipelines in the selector (e.g. Marketing, Sales, CS).List groups
GET
/backend/pipeline/groupsCreate a group
POST
/backend/pipeline/groupsGroup name
Rename a group
PUT
/backend/pipeline/groups/{id}New group name
Delete a group
DELETE
/backend/pipeline/groups/{id}409 Conflict
Error
message strings are returned by the API in Portuguese. Match on code
(ERR_CONFLICT), never on the message text.