Skip to content

Zoho: Delete a custom layout

Zoho layouts.deleteLayout: arguments, response, policy and SDK examples.

← Layouts operations · Get started

Operation zoho.deletelayout

Provider route: DELETE /crm/v8/settings/layouts/{id}. Alter supplies the connection’s credentials and routing.

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["layouts"]["deleteLayout"]>[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.layouts.deleteLayout(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.layouts.delete_layout(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
pathobjectRequired within parentAdditional keys: not allowed
path.idstringRequired within parentRepresents a unique numeric identifier for a CRM entity, expressed as a 64-bit integer serialized as a string to preserve precision in JSON.
Format: int64
Maximum length: 19
Minimum length: 1
Pattern: ^[0-9]{1,19}$
queryobjectRequired within parentAdditional keys: not allowed
query.modulestringRequired within parentUnique API identifier for the module used in third-party integrations; starts with a letter, contains only alphanumeric characters and underscores, and has no consecutive or trailing underscores.
Maximum length: 50
query.transfer_tostringOptionalRepresents a unique numeric identifier for a CRM entity, expressed as a 64-bit integer serialized as a string to preserve precision in JSON.
Format: int64
Maximum length: 19
Minimum length: 1
Pattern: ^[0-9]{1,19}$
query.pipelinestringOptionalRepresents a unique numeric identifier for a CRM entity, expressed as a 64-bit integer serialized as a string to preserve precision in JSON.
Format: int64
Maximum length: 19
Minimum length: 1
Pattern: ^[0-9]{1,19}$
query.stagestringOptionalRepresents a unique numeric identifier for a CRM entity, expressed as a 64-bit integer serialized as a string to preserve precision in JSON.
Format: int64
Maximum length: 19
Minimum length: 1
Pattern: ^[0-9]{1,19}$

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

FieldTypePresenceDescription and constraints
$ModelRootExpand Delete a custom layout — response body

Referenced models: Delete a custom layout — response body

Delete a custom layout — response body
FieldTypePresenceDescription and constraints
$objectRootRepresents the response body returned when one or more layouts are successfully deleted, containing per-layout deletion results.
Additional keys: not allowed
layoutsarrayRequired within parentContains one entry per layout included in the deletion request, each reporting the individual outcome — such as success or failure — for that specific layout.
Maximum items: 1
Minimum items: 1
layouts[]ModelEach itemExpand Delete a custom layout — response body — layouts item

Referenced models: Delete a custom layout — response body — layouts item

Delete a custom layout — response body — layouts item
FieldTypePresenceDescription and constraints
$objectRootRepresents the outcome of a single layout deletion attempt within a batch operation, including a status code and descriptive message for that layout.
Additional keys: not allowed
codestringRequired within parentIndicates the outcome code returned for the layout deletion attempt. Possible values: `SUCCESS` — the layout deletion completes successfully.
Known values: SUCCESS
detailsModelRequired within parentExpand Delete a custom layout — response body — layouts item details
messagestringRequired within parentContains a descriptive message summarising the outcome of the layout deletion operation, providing context for both successful completions and failure conditions.
Maximum length: 500
statusstringRequired within parentRepresents the overall processing state of the layout deletion request. Possible values: `success` — the layout was removed as requested.
Known values: success

Referenced models: Delete a custom layout — response body — layouts item details

Delete a custom layout — response body — layouts item details
FieldTypePresenceDescription and constraints
$objectRootRepresents the identifying details of a layout that has been successfully deleted, returned in the deletion response to confirm which layout was removed.
Additional keys: not allowed
idstringRequired within parentRepresents a unique numeric identifier for a CRM entity, expressed as a 64-bit integer serialized as a string to preserve precision in JSON.
Unique identifier of the deleted layout.
Format: int64
Maximum length: 19
Minimum length: 1
Pattern: ^[0-9]{1,19}$

SDK function policy ID: zoho.deletelayout. Catalog operation: deleteLayout. 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

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.