For AI agents: markdown of this page — /docs-content-en/entities/bizproc-activities/update.md documentation index — /llms.txt

Update an activity

PATCH /v1/bizproc-activities/:code

Updates a previously registered business process activity. Pass only the fields you change, flat at the JSON root — without a fields wrapper. The method works only with an authorization key together with the Authorization: Bearer header.

Parameters

Parameter Type Required Description
Parametercode (path) Typestring RequiredYes DescriptionActivity code

Request fields (body)

Field Type Description
Fieldname Typestring | object DescriptionActivity name. A string or a localized object like {"en": "...", "de": "..."}
Fieldhandler Typestring DescriptionActivity handler URL. The domain must match the application domain
Fielddescription Typestring | object DescriptionActivity description. A string or a localized object
FieldauthUserId Typenumber DescriptionID of the user whose token is passed to the application when the activity is called. List: GET /v1/users
FielduseSubscription Typestring DescriptionWhether to wait for the application's response before continuing the process: Y or N
Fieldproperties Typeobject DescriptionActivity input parameters
FieldreturnProperties Typeobject DescriptionActivity output parameters
FielddocumentType Typearray DescriptionDocument type: [module, object, type]
Fieldfilter Typeobject DescriptionLimits which documents the activity is available for. An empty object {} removes the restriction.
INCLUDE lists the conditions under which the activity is available, EXCLUDE those under which it is not. A condition is a document type prefix, for example ["crm", "CCrmDocumentDeal"], or a Bitrix24 edition: "b24" for cloud, "box" for on-premise.
Example: {"INCLUDE": [["crm", "CCrmDocumentDeal"], ["crm", "CCrmDocumentLead"]]}.
Write the keys in uppercase: with lowercase keys the field is accepted but restricts nothing. A value that is not an object returns 422 BITRIX_ERROR
FieldusePlacement Typestring DescriptionWhether to open the activity settings in a slider panel: Y or N
FieldplacementHandler Typestring DescriptionURL of the settings slider panel. Required when usePlacement: "Y"

Examples

The session token is issued by OAuth authorization, is valid for 24 hours, and cannot be renewed — Passing the key.

curl — OAuth application

Terminal 
curl -X PATCH "https://vibecode.bitrix24.com/v1/bizproc-activities/notify_manager" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": { "en": "Notify department manager", "de": "Abteilungsleiter benachrichtigen" }
  }'

JavaScript — OAuth application

javascript 
const res = await fetch('https://vibecode.bitrix24.com/v1/bizproc-activities/notify_manager', {
  method: 'PATCH',
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    name: { en: 'Notify department manager', de: 'Abteilungsleiter benachrichtigen' },
  }),
})

const { success, data } = await res.json()

Response fields

Field Type Description
Fieldsuccess Typeboolean DescriptionAlways true on success
Fielddata.id Typestring DescriptionThe code of the updated activity — matches code from the path

Response example

JSON 
{
  "success": true,
  "data": {
    "id": "notify_manager"
  }
}

Error response example

422 — no activity with the given code was found:

JSON 
{
  "success": false,
  "error": {
    "code": "BITRIX_ERROR",
    "message": "Activity or Robot not found!",
    "b24Code": "ERROR_ACTIVITY_NOT_FOUND"
  }
}

Errors

HTTP Code Description
HTTP401 CodeTOKEN_MISSING DescriptionThe authorization key was sent without the Authorization: Bearer header
HTTP401 CodeWRONG_AUTH_SCHEME DescriptionThe authorization key was sent in the Authorization: Bearer header. The key goes in X-Api-Key, while Authorization: Bearer carries the session token
HTTP401 CodeINVALID_SESSION DescriptionThe session token has expired or is invalid — authorize again
HTTP403 CodeOAUTH_REQUIRED DescriptionThe request was sent with an API key. Only an authorization key can update activities
HTTP403 CodeSCOPE_DENIED DescriptionThe key lacks the bizproc scope
HTTP400 CodeSERVER_APP_MISMATCH DescriptionThe new handler points to a Black Hole subdomain that has no server of this app behind it — the subdomain does not exist, or the server belongs to another app
HTTP409 CodeBIZPROC_MODULE_NOT_ENABLED DescriptionBusiness Processes are not available on the account: the module is not included in the plan, or it is switched off in account settings. Ask an account administrator to enable Business Processes — until then the method answers the same way for any number of retries
HTTP503 CodeBIZPROC_CALLBACK_RESOLVE_FAILED DescriptionThe platform could not match the handler to a server. The activity was not updated — retry the request
HTTP422 CodeBITRIX_ERROR DescriptionBitrix24 did not find an activity with the given code or rejected the update — the reason is in error.message

The full list of common API errors — Errors.

Known specifics

Moving the handler to a Black Hole subdomain switches the activity to reliable delivery. Moving back to an address on your own domain restores direct calls without retries, and a request without the handler field leaves the binding unchanged. A switch to a subdomain must be sent as a single request — Activity and automation rule callback delivery.

See also