Add Price Type Binding to Customer Group catalog.priceTypeGroup.add

If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.

Scope: catalog

Who can execute the method: user with "Manage Price Types" access permission

The method catalog.priceTypeGroup.add adds a price type binding to a customer group.

Method Parameters

Required parameters are marked with *

Name `type`	Description
fields* `object`	Field values for creating a price type binding to a customer group (detailed description)

Parameter fields

Required parameters are marked with *

Name `type`	Description
catalogGroupId* `catalog_price_type.id`	Identifier of the price type. Can be obtained using the catalog.priceType.list method
groupId* `integer`	Identifier of the customer group
access* `char`	Type of access to the price. Possible values: `Y` — right to purchase at this price type `N` — right to view this price type

Before adding, check for an existing record using the catalog.priceTypeGroup.list method with filters for catalogGroupId, groupId, and access. If the record already exists, the method will return an error: The specified access type for this group already exists

Code Examples

How to Use Examples in Documentation

cURL (Webhook)

cURL (OAuth)

PHP

BX24.js

PHP CRest

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"fields":{"catalogGroupId":9,"groupId":23,"access":"Y"}}' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/catalog.priceTypeGroup.add

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"fields":{"catalogGroupId":9,"groupId":23,"access":"Y"},"auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/catalog.priceTypeGroup.add

try
        {
        	const response = await $b24.callMethod(
        		'catalog.priceTypeGroup.add',
        		{
        			fields: {
        				catalogGroupId: 9,
        				groupId: 23,
        				access: "Y"
        			}
        		}
        	);
        	
        	const result = response.getData().result;
        	console.log(result);
        }
        catch( error )
        {
        	console.error(error.ex);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'catalog.priceTypeGroup.add',
                    [
                        'fields' => [
                            'catalogGroupId' => 9,
                            'groupId'        => 23,
                            'access'         => 'Y',
                        ],
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            if ($result->error()) {
                error_log($result->error()->ex);
            } else {
                echo 'Success: ' . print_r($result->data(), true);
            }
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error adding price type group: ' . $e->getMessage();
        }

BX24.callMethod(
            'catalog.priceTypeGroup.add',
            {
                fields: {
                    catalogGroupId: 9,
                    groupId: 23,
                    access: 'Y'
                }
            },
            function(result) {
                if (result.error())
                    console.error(result.error().ex);
                else
                    console.log(result.data());
            }
        );

require_once('crest.php');
        
        $result = CRest::call(
            'catalog.priceTypeGroup.add',
            [
                'fields' => [
                    'catalogGroupId' => 9,
                    'groupId' => 23,
                    'access' => 'Y'
                ]
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';

Response Handling

HTTP Status: 200

{
            "result": {
                "priceTypeGroup": {
                "access": "Y",
                "catalogGroupId": 9,
                "groupId": 23,
                "id": 109
                }
            },
            "time": {
                "start": 1774260171,
                "finish": 1774260171.438073,
                "duration": 0.43807291984558105,
                "processing": 0,
                "date_start": "2026-03-23T13:02:51+01:00",
                "date_finish": "2026-03-23T13:02:51+01:00",
                "operating_reset_at": 1774260771,
                "operating": 0
            }
        }

Returned Data

Name `type`	Description
result `object`	Root element of the response
priceTypeGroup `catalog_price_type_group`	Object containing information about the created price type binding to the customer group
time `time`	Information about the request execution time

Error Handling

HTTP Status: 400

{
            "error": 200040300020,
            "error_description": "Access Denied"
        }

Name `type`	Description
error `string`	String error code. It may consist of digits, Latin letters, and underscores
error_description `error_description`	Textual description of the error. The description is not intended to be shown to the end user in its raw form

Possible Error Codes

Code	Description	Value
`200040300020`	Access Denied	Insufficient rights to edit price types
`100`	Could not find value for parameter	Required parameter `fields` not provided
`0`	The specified price type does not exist	The specified price type does not exist
`0`	The specified group does not exist	The specified customer group does not exist
`0`	Invalid access type provided. The available values are: Y, N	Invalid access type provided. Available values: `Y`, `N`
`0`	The specified access type for this group already exists	This binding for this price type and group already exists

Statuses and System Error Codes

HTTP Status: 20x, 40x, 50x

The errors described below may occur when calling any method.

Status	Code Error Message	Description
`500`	`INTERNAL_SERVER_ERROR` Internal server error	An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support
`500`	`ERROR_UNEXPECTED_ANSWER` Server returned an unexpected response	An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support
`503`	`QUERY_LIMIT_EXCEEDED` Too many requests	The request intensity limit has been exceeded
`405`	`ERROR_BATCH_METHOD_NOT_ALLOWED` Method is not allowed for batch usage	The current method is not permitted for calls using batch
`400`	`ERROR_BATCH_LENGTH_EXCEEDED` Max batch length exceeded	The maximum length of parameters passed to the batch method has been exceeded
`401`	`NO_AUTH_FOUND` Wrong authorization data	Invalid access token or webhook code
`400`	`INVALID_REQUEST` Https required	The HTTPS protocol is required for method calls
`503`	`OVERLOAD_LIMIT` REST API is blocked due to overload	The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it
`403`	`ACCESS_DENIED` REST API is available only on commercial plans	The REST API is only available on commercial plans
`403`	`INVALID_CREDENTIALS` Invalid request credentials	The user associated with the access token or webhook used to call the method lacks the necessary permissions
`404`	`ERROR_MANIFEST_IS_NOT_AVAILABLE` Manifest is not available	The manifest is not available
`403`	`insufficient_scope` The request requires higher privileges than provided by the webhook token	The request requires higher privileges than those provided by the webhook token
`401`	`expired_token` The access token provided has expired	The provided access token has expired
`403`	`user_access_error` The user does not have access to the application	The user does not have access to the application. This means that the application is installed, but the portal administrator has restricted access to this application to specific users only
`500`	`PORTAL_DELETED` Portal was deleted	The public part of the site is closed. To open the public part of the site 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

Overview of Methods

Get List of Bindings

Add Price Type Binding to Customer Group catalog.priceTypeGroup.add

Method ParametersMethod Parameters

Parameter fieldsParameter fields

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

Error HandlingError Handling

Possible Error CodesPossible Error Codes

Statuses and System Error CodesStatuses and System Error Codes

Continue LearningContinue Learning