Zoho: Remove territories from a user

← Users territories operations · Get started

Operation zoho.removeterritoriesfromuser

Provider route: DELETE /crm/v8/users/{user}/territories. Alter supplies the connection’s credentials and routing.

Call through Alter

Install @alter-ai/sdk @alter-ai/zoho with npm, or alter-sdk-zoho with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { ZohoIntegration } from "@alter-ai/zoho";

async function execute(input: Parameters<ZohoIntegration["usersTerritories"]["removeTerritoriesfromUser"]>[0]) {
  const app = new App({ apiKey: process.env.ALTER_API_KEY! });
  try {
    const provider = new ZohoIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
    const call = await provider.usersTerritories.removeTerritoriesfromUser(input);
    const result = await call.wait();
    return result.bodyJson();
  } finally {
    await app.close();
  }
}

import os
from alter_sdk import App
from alter_sdk_zoho import ZohoIntegration

async def execute(arguments):
    async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
        provider = ZohoIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
        call = await provider.users_territories.remove_territoriesfrom_user(arguments)
        result = await call.wait()
        return result.body_json()

Input

Field	Type	Presence	Description and constraints
$	object	Root	Additional keys: not allowed
path	object	Required within parent	Additional keys: not allowed
path.user	string	Required within parent	Format: int64
query	object	Required within parent	Additional keys: not allowed
query.ids	string	Required within parent	Comma-separated IDs (digits only, separated by commas) Maximum length: 2000 Pattern: ^[0-9]+(,[0-9]+)*$

Response

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

Field	Type	Presence	Description and constraints
$	Model	Root	Expand Add territories to a user — response body

Referenced models: Add territories to a user — response body

Schemas

Add territories to a user — response body

Field	Type	Presence	Description and constraints
$	object	Root	Represents the response containing the per-territory operation results. Additional keys: not allowed
territories	array	Required within parent	Represents the list of per-territory operation results. Maximum items: 200 Minimum items: 0 Unique items: true
territories[]	object	Each item	Represents the result of a single territory operation. Additional keys: not allowed
territories[].code	string	Required within parent	Represents the result code for the territory operation. Possible values: SUCCESS - The territory operation completed successfully. Known values: SUCCESS
territories[].details	object	Required within parent	Represents the additional details for the operation result. Additional keys: not allowed
territories[].details.id	string	Required within parent	Represents the unique ID of the territory on which the operation was performed. Format: int64
territories[].message	string	Required within parent	Represents the message describing the result of the territory operation. Maximum length: 1000
territories[].status	string	Required within parent	Represents the status of the territory operation. Possible values: success - The operation completed successfully. Known values: success

Policy, approvals and errors

SDK function policy ID: zoho.removeterritoriesfromuser. Catalog operation: removeTerritoriesfromUser. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Official provider source