Add a Kanban or "My Plan" Stage task.stages.add

Choose a tool for developing with an AI agent:

  • use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
  • use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation

Scope: task

Who can execute the method:

  • any user for "My Plan" stages
  • any user with group access for Kanban stages

The method task.stages.add adds a Kanban or "My Plan" stage.

Method Parameters

Required parameters are marked with *

Name
type

Description

fields*
object

Field values (detailed description provided below) for adding a new stage

isAdmin
boolean

If set to true, permission checks will not occur, provided the requester is an administrator of the account

Parameter fields

Required parameters are marked with *

Name
type

Description

TITLE*
string

Stage title

COLOR
string

Stage color in RGB format

AFTER_ID
integer

Identifier of the stage after which the new stage should be added.

If not specified or equal to 0, it will be added at the beginning

ENTITY_ID
integer

Object identifier.

Can equal the ID of the group, in which case the stage will be added to the group's Kanban.

If equal to 0 or absent, the stage will be added to "My Plan" of the current user.

An access error will be returned if the permission level is insufficient

Code Examples

How to Use Examples in Documentation

curl -X POST \
        -H "Content-Type: application/json" \
        -d '{
        "fields": {
            "TITLE": "Stage title",
            "COLOR": "#FFAAEE",
            "AFTER_ID": 1,
            "ENTITY_ID": 1
        },
        "isAdmin": false
        }' \
        https://your-domain.bitrix24.com/rest/_USER_ID_/_CODE_/task.stages.add
        
curl -X POST \
        -H "Content-Type: application/json" \
        -H "Authorization: YOUR_ACCESS_TOKEN" \
        -d '{
        "fields": {
            "TITLE": "Stage title",
            "COLOR": "#FFAAEE",
            "AFTER_ID": 1,
            "ENTITY_ID": 1
        },
        "isAdmin": false
        }' \
        https://your-domain.bitrix24.com/rest/task.stages.add
        
// This snippet is an ES module: top-level await requires type="module" or a bundler.
        // $b24 is an already-initialized SDK instance (see the SDK "Get started" guide).
        import { Text } from '@bitrix24/b24jssdk'
        import type { B24Frame } from '@bitrix24/b24jssdk'
        
        declare const $b24: B24Frame
        
        // ID of the added stage returned in result
        // Shape of the payload returned in result (match the "response handling" section of the page)
        type StageAddResult = number
        
        try {
          const response = await $b24.actions.v2.call.make<StageAddResult>({
            method: 'task.stages.add',
            params: {
              fields: {
                TITLE: 'Stage title',
                COLOR: '#FFAAEE',
                AFTER_ID: 1,
                ENTITY_ID: 1,
              },
              isAdmin: false,
            },
            requestId: Text.getUuidRfc4122()
          })
        
          // The payload is available only on a successful response
          if (!response.isSuccess) {
            console.error(response.getErrorMessages().join('; '))
          } else {
            const result = response.getData()!.result
            console.info('New stage ID:', result)
          }
        } catch (error) {
          // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
          console.error(error)
        }
        
<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
        <script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
        <script>
          async function addTaskStage() {
            try {
              // Initialize the SDK inside a Bitrix24 frame
              const $b24 = await B24Js.initializeB24Frame()
        
              const response = await $b24.actions.v2.call.make({
                method: 'task.stages.add',
                params: {
                  fields: {
                    TITLE: 'Stage title',
                    COLOR: '#FFAAEE',
                    AFTER_ID: 1,
                    ENTITY_ID: 1,
                  },
                  isAdmin: false,
                },
                requestId: B24Js.Text.getUuidRfc4122()
              })
        
              // The payload is available only on a successful response
              if (!response.isSuccess) {
                console.error(response.getErrorMessages().join('; '))
                return
              }
        
              const result = response.getData().result
              console.info('New stage ID:', result)
            } catch (error) {
              // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
              console.error(error)
            }
          }
        
          document.addEventListener('DOMContentLoaded', addTaskStage)
        </script>
        
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
        
        fields = {
            "TITLE": "Stage name",
            "COLOR": "#FFAAEE",
            "AFTER_ID": 1,
            "ENTITY_ID": 1,
        }
        
        try:
            bitrix_response = client.task.stages.add(
                fields=fields,
                is_admin=False,
            ).response
            result = bitrix_response.result
            print(result)
        except BitrixAPIError as error:
            print(
                "Bitrix API error",
                f"error: {error.error}",
                f"error_description: {error.error_description}",
                sep="\n",
            )
        except BitrixSDKException as error:
            print(f"Bitrix SDK error: {error.message}")
        except Exception as error:
            print(f"Unexpected error: {error}")
        
try {
            $response = $b24Service
                ->core
                ->call(
                    'task.stages.add',
                    [
                        'fields' => [
                            'TITLE'    => 'Stage title',
                            'COLOR'    => '#FFAAEE',
                            'AFTER_ID' => 1,
                            'ENTITY_ID' => 1
                        ],
                        'isAdmin' => false,
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . print_r($result, true);
            // Your logic for processing data
            processData($result);
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error adding task stage: ' . $e->getMessage();
        }
        
BX24.callMethod(
            'task.stages.add',
            {
                fields: {
                    TITLE: 'Stage title',
                    COLOR: '#FFAAEE',
                    AFTER_ID: 1,
                    ENTITY_ID: 1
                },
                isAdmin: false,
            },
            function(result) {
                if (result.error()) {
                    console.error(result.error());
                } else {
                    console.info(result.data());
                }
            }
        );
        
require_once('crest.php'); // include CRest PHP SDK
        
        $fields = [
            "TITLE" => "Stage title",
            "COLOR" => "#FFAAEE",
            "AFTER_ID" => 1,
            "ENTITY_ID" => 1
        ];
        
        // execute request to REST API
        $result = CRest::call(
            'task.stages.add',
            [
                'fields' => $fields,
                'isAdmin' => false
            ]
        );
        
        // Process the response from Bitrix24
        if ($result['error']) {
            echo 'Error: '.$result['error_description'];
        } else {
            print_r($result['result']);
        }
        
// client and ctx are already created — see the Go SDK section
        res, err := client.Core().Call(ctx, "task.stages.add", b24.Params{
        	"fields": b24.Params{
        		"TITLE":     "Stage title",
        		"COLOR":     "#FFAAEE",
        		"AFTER_ID":  1,
        		"ENTITY_ID": 1,
        	},
        	"isAdmin": false,
        })
        if err != nil {
        	return fmt.Errorf("task.stages.add: %w", err)
        }
        
        var newID b24.ID
        if err := json.Unmarshal(res.Result, &newID); err != nil {
        	return fmt.Errorf("parse response: %w", err)
        }
        fmt.Println("id:", newID)
        

Response Handling

HTTP Status: 200

{
            "result": 1
        }
        

Returned Data

Name
type

Description

result
integer

Identifier of the added stage

Error Handling

HTTP Status: 400

{
            "error": "EMPTY_TITLE",
            "error_description": "Stage title is not specified"
        }
        

Name
type

Description

error
string

String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only error_description shows the reason

error_description
string

Error message for the developer. Do not show it to the end user without processing

Possible Error Codes

Code

Description

EMPTY_TITLE

Stage title is not specified

ACCESS_DENIED

You do not have permission to manage stages

Statuses and System Error Codes

HTTP Status: 4xx, 5xx

The errors described below are returned by the REST API itself, not by the logic of a specific method. They can arrive in response to any method.

Status

Code
Error Message

Description

500

INTERNAL_SERVER_ERROR
Internal server error

An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support

500

ERROR_UNEXPECTED_ANSWER
Server returned an unexpected response

The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support

503

QUERY_LIMIT_EXCEEDED
Too many requests

The request intensity limit has been exceeded

429

OPERATION_TIME_LIMIT
Method is blocked due to operation time limit

The method is blocked because the request resource intensity limit has been exceeded. The block is lifted automatically once the accumulated execution time of the method no longer exceeds the limit

401

NO_AUTH_FOUND
Wrong authorization data

The request contains no authorization data: neither an access token nor a webhook code was passed

401

INVALID_REQUEST
Https required

Methods are called over the HTTPS protocol only

401

OVERLOAD_LIMIT
REST API is blocked due to overload

The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support

401

ACCESS_DENIED
REST is available only on commercial plans

REST API access is not active for this account. In Bitrix24 Cloud, check the current plan or trial status: Vibe+ plans include REST API access, while Essentials plans do not. A webhook receives a different error message — REST is available only by subscription

401

INVALID_CREDENTIALS
Invalid request credentials

No active webhook with the specified user identifier and secret code was found

404

ERROR_METHOD_NOT_FOUND
Method not found!

No method with this name was found. The name is misspelled, the method does not exist in the REST API, or it is unavailable without the required scope

401

insufficient_scope
The request requires higher privileges than provided by the webhook token

The request requires broader permissions than the token has: for a webhook these are the permissions granted to it, for an application it is the scope. For an application, the error message ends with provided by the access token

401

expired_token
The access token provided has expired

The access token has expired

401

user_access_error
The user does not have access to the application

The application is installed, but the Bitrix24 administrator has granted access to it only to specific users

403

PORTAL_DELETED
Portal was deleted

The public part of the site is closed. To open it on an on-premise installation, disable the "Temporary closure of the public part of the site" option. Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site

Continue Learning