When to use this endpoint

Use AccountCategoryGroup_delete for CRM1’s Tax Group delete control. Categories assigned to the group become ungrouped.

Authentication and permissions

The request must establish an authenticated tenant context with signed API credentials or a logged-in CRM session. This legacy handler checks for the tenant database prefix rather than calling the normal login guard.

It performs no additional Finance-page, client-admin, role, create, edit, or delete permission check.

Parameters

ParameterTypeRequiredDescription
idInteger-compatibleYesPositive category-group ID.

Example request

$result = FM_api('AccountCategoryGroup_delete', [
	'id' => 151003,
]);

Example response

{"ok":1}

Errors and unusual responses

ResponseCondition
{"error":"not logged in"}No authenticated tenant context is available. Invalid signed credentials can be rejected by the dispatcher before the handler runs.
{"error":"missing or invalid parameter: id"}The ID is absent or not positive.

Legacy application errors may be returned with HTTP 200. Check the decoded response for error, not only the HTTP status.

Behaviour and edge cases

  • An unknown positive ID is a silent no-op that returns success.
  • There is no deletion log, restore route, dependency check, or transaction.

Side effects

  • Clears matching category group references, updates their timestamps, and clears the category cache.
  • Deletes the tenant account_category_groups row and clears that table’s cache.

See it in Fieldmotion

CRM1

Open Settings → Finance. CRM1 loads and edits the Chart of Accounts, Tax Types, and Tax Groups from this endpoint family; filter browser developer tools for the exact function name. Delete a Tax Group row to send this endpoint.

CRM2

CRM2 does not call this focused route; omitted groups are deleted by AccountCategoryGroup_updateData during Save.

Related endpoints