Skip to content

HighLevel: Create Custom Object

HighLevel objects.createCustomObjectSchema: arguments, response, policy and SDK examples.

← Objects operations · Get started

Operation gohighlevel.create_custom_object_schema

Provider route: POST /objects/. Alter supplies the connection’s credentials and routing.

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

import { App } from "@alter-ai/sdk";
import { HighLevelIntegration } from "@alter-ai/gohighlevel";
async function execute(input: Parameters<HighLevelIntegration["objects"]["createCustomObjectSchema"]>[0]) {
const app = new App({ apiKey: process.env.ALTER_API_KEY! });
try {
const provider = new HighLevelIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
const call = await provider.objects.createCustomObjectSchema(input);
const result = await call.wait();
return result.bodyJson();
} finally {
await app.close();
}
}
import os
from alter_sdk import App
from alter_sdk_gohighlevel import HighLevelIntegration
async def execute(arguments):
async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
provider = HighLevelIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
call = await provider.objects.create_custom_object_schema(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
bodyModelRequired within parentExpand Create Custom Object — request body — body

Referenced models: Create Custom Object — request body — body

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

FieldTypePresenceDescription and constraints
$ModelRootExpand Create Custom Object — response body

Referenced models: Create Custom Object — response body

Create Custom Object — request body — body
FieldTypePresenceDescription and constraints
$objectRoot
descriptionstringOptionalPet Object`s description
keystringRequired within parentkey that would be used to refer the Custom Object internally (lowercase + underscore_separated). 'custom_objects.' would be added as prefix by default
labelsJSONRequired within parentThis is what your custom object will be called. These labels will be used to display your custom object on the UI
labels (allOf 1)ModelAll variants applyExpand Create Custom Object — request body — body labels plural, singular
locationIdstringRequired within parentLocation Id
primaryDisplayPropertyDetailsJSONRequired within parentPrimary property which will be displayed on the record page
primaryDisplayPropertyDetails (allOf 1)ModelAll variants applyExpand Create Custom Object — request body — body primary Display Property Details data Type, key, name

Referenced models: Create Custom Object — request body — body primary Display Property Details data Type, key, name, Create Custom Object — request body — body labels plural, singular

Create Custom Object — response body
FieldTypePresenceDescription and constraints
$objectRoot
objectModelOptionalExpand Create Custom Object — response body — object

Referenced models: Create Custom Object — response body — object

Create Custom Object — request body — body primary Display Property Details data Type, key, name
FieldTypePresenceDescription and constraints
$objectRoot
dataTypestringRequired within parentPrimary property data Type (it can either be TEXT or NUMERICAL type)
keystringRequired within parentkey that would be used to refer the custom field internally (lowercase + underscore_separated). 'custom_objects.{{objectKey}}' would be added as prefix by default is not passed
namestringRequired within parentName of the Primary property name which will be displayed on the record page
Create Custom Object — request body — body labels plural, singular
FieldTypePresenceDescription and constraints
$objectRoot
pluralstringRequired within parentPlural name of the custom object
singularstringRequired within parentSingular name of the custom object
Create Custom Object — response body — object
FieldTypePresenceDescription and constraints
$objectRoot
dateAddedstringRequired within parentDate and time when the object was added
Format: date-time
dateUpdatedstringRequired within parentDate and time when the object was last updated
Format: date-time
descriptionstringOptionalCustom / Standard Object Descriptions for example , Pet Object`s description
idstringRequired within parentid of the custom / standard object schema
keystringRequired within parentkey that would be used to refer the custom / standard Object internally (lowercase + underscore_separated). For custom objects, 'custom_objects.' would be added as prefix by default
labelsJSONRequired within parentThis is what your custom / standard object will be called. These labels will be used to display your custom object on the UI
labels (allOf 1)ModelAll variants applyExpand Create Custom Object — request body — body labels plural, singular
locationIdstringRequired within parentlocation's id
primaryDisplayPropertystringRequired within parentPrimary property for the custom / standard Object. This would be used as primary data when rendering the UI. 'custom_objects.{{object_key}} or business.{{object_key}} (for company)' would be added as prefix by default for all the custom / standard objects
standardbooleanRequired within parentfalse in case of custom objects and true in case of standard objects like contacts and opportunities
typeobjectOptionalObject`s Type

Referenced models: Create Custom Object — request body — body labels plural, singular

SDK function policy ID: gohighlevel.create_custom_object_schema. Catalog operation: create-custom-object-schema. 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.

Required provider scopes: ["objects/schema.write"]

Pinned headers: {"Version": "v3"}

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.