Skip to content

HighLevel: Email Verification

HighLevel emailIsv.verifyEmail: arguments, response, policy and SDK examples.

← Email isv operations · Get started

Operation gohighlevel.verify_email

Provider route: POST /email/verify. 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["emailIsv"]["verifyEmail"]>[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.emailIsv.verifyEmail(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.email_isv.verify_email(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
queryobjectRequired within parentAdditional keys: not allowed
query.locationIdstringRequired within parent
bodyModelRequired within parentExpand Email Verification — request body — body

Referenced models: Email Verification — 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
$JSONRoot
$ (anyOf 1)ModelAlternativeExpand Email Verification — response body — result: deliverable, undeliverable, do not send, unknown, catch all, risk: high, low, medium, unknown
$ (anyOf 2)ModelAlternativeExpand Email Verification — response body — address, message, verified
$ (anyOf 3)ModelAlternativeExpand Email Verification — response body — is Email Valid

Referenced models: Email Verification — response body — address, message, verified, Email Verification — response body — is Email Valid, Email Verification — response body — result: deliverable, undeliverable, do not send, unknown, catch all, risk: high, low, medium, unknown

Email Verification — response body — address, message, verified
FieldTypePresenceDescription and constraints
$objectRoot
addressstringOptionalEmail address
messagestringOptionalEmail verification failure message
verifiedbooleanRequired within parentEmail verification not processed
Email Verification — response body — is Email Valid
FieldTypePresenceDescription and constraints
$objectRoot
isEmailValidbooleanOptionalEmail verification status
Email Verification — response body — result: deliverable, undeliverable, do not send, unknown, catch all, risk: high, low, medium, unknown
FieldTypePresenceDescription and constraints
$objectRoot
addressstringRequired within parentEmail address
leadConnectorRecommendationJSONOptionalLead Connector email verification recommendation
leadConnectorRecommendation (allOf 1)ModelAll variants applyExpand Email Verification — response body — is Email Valid
reasonarrayOptionalReason for email verification failure
reason[]stringEach item
resultstringRequired within parentEmail verification result
Known values: deliverable, undeliverable, do_not_send, unknown, catch_all
riskstringRequired within parentRisk level of email sending to bounce
Known values: high, low, medium, unknown

Referenced models: Email Verification — response body — is Email Valid

Email Verification — request body — body
FieldTypePresenceDescription and constraints
$objectRoot
typestringRequired within parentEmail Verification type
One of: email, contact
verifystringRequired within parentEmail Verification recepient (email address / contactId)

SDK function policy ID: gohighlevel.verify_email. Catalog operation: verify-email. 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: ["lc-email.readonly"]

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.