01Who this is for
- Agencies that manage many client locations can automate brand voice setup for consistency.
- SaaS platforms can embed brand voice provisioning into their onboarding flow.
- Developers building integrations need programmatic control over brand identity across accounts.
02Brand voice APIs, explained
The Brand Voice API exposes HTTP endpoints that let external systems manage brand voices inside HighLevel. You can list voices, fetch a single voice, create new ones, modify existing records, delete voices, and set a default voice for a location.
All endpoints are scoped to a location identifier. Creation requires a type field that selects manual, URL, or description mode. Manual mode needs explicit brand details, while the AI generated modes use a website URL or a text description. Updates accept any subset of fields, changing only what is sent.
The API lives in the HighLevel developer resources and is accessed like any other HighLevel API endpoint, following standard authentication and versioning practices.
03How businesses use brand voice APIs
- Digital marketing agency. The agency calls the POST endpoint to add a brand voice for each client location using manual mode. They later use PATCH to adjust tone when a client rebrands. The default voice is set with the dedicated endpoint.
- SaaS platform. During user sign up the platform sends a URL mode request to generate a brand voice from the new user's website. The created voice is stored via the API and used by the platform’s AI content features.
- Ecommerce store. When launching a new product line, the store sends a description mode request to create a brand voice that reflects the new line. They update only the target audience field with PATCH to refine messaging.
04How to set up and use brand voice APIs in HighLevel
Retrieve a list of brand voices for a location
- Send a GET request to /locations/:locationId/voices and handle pagination, search, or filter parameters as needed.
Retrieve details of a specific brand voice
- Send a GET request to /locations/:locationId/voices/:brandVoiceId to receive full voice data.
Create a new brand voice
- Send a POST request to /locations/:locationId/voices with the required type field and, if using manual mode, include brandName, toneOfVoice, targetAudience, and customerPainPoints.
Update an existing brand voice
- Send a PATCH request to /locations/:locationId/voices/:brandVoiceId containing only the fields that need changes.
Delete a brand voice
- Send a DELETE request to /locations/:locationId/voices/:brandVoiceId.
Set a brand voice as the default for a location
- Send a POST request to /locations/:locationId/voices/:brandVoiceId/default.
05Settings that matter
- type. Specifies the creation mode; must be manual, url, or description.
06Things to know before you rely on it
- Manual creation requires brandName, toneOfVoice, targetAudience, and customerPainPoints fields.
- When type is url or description, manual fields cannot be included.
- Only one default voice can be set per location.
- All fields are optional for PATCH updates; only supplied fields are changed.
07If something goes wrong
- Incorrect fields sent for the selected creation mode. Check that the request includes only the fields allowed for the chosen type.
- Attempt to recover a deleted brand voice. Confirm the need before deleting; retrieval may not be guaranteed.
08How it connects to the rest of HighLevel
- Select the API version you need before making calls API version guide
- Test webhook payloads and responses during integration Webhook testing guide
- Review pricing and plan options for API access Pricing
Michael's take

Getting into brand voice APIs can feel heavy if you don’t have a solid integration pipeline. The endpoints expect exact field structures and the right type value, so a stray property will trip a validation error.