Skip to content

[Bug Report: API Field Missing] GET API needed for SMS Conversation Channel configuration (Already exists, just make it public) #243

@carlosm2498

Description

@carlosm2498

🐛 Describe the Bug

The API for retrieving SMS conversation channel configuration for a location is not publicly available, even though this information exists and is configurable in the HighLevel UI.

As a custom SMS provider marketplace app, we have no programmatic way to determine whether a customer has changed their SMS provider settings after installing our app.

This creates repeated support loops where customers report “SMS not working,” but we cannot verify if they have switched providers, disabled our provider, or misconfigured the SMS channel — because there is no GET API to read this configuration.

📍 API Endpoint

GET /locations/{locationId}/conversationChannels/SMS

✅ Expected Behavior

A public GET API should be available that returns the current SMS conversation channel configuration for a location, including:

  • Whether a custom provider is enabled
  • Which provider is currently selected
  • This information is already present in the UI and should be readable via API.

💻 Screenshots or Code Samples

No response

Product Area

lc-phone-sms

📋 Use Case

We are a custom SMS provider marketplace integration.

We need this API to:

  • Detect if the customer has changed the SMS provider away from ours
  • Detect misconfiguration without relying on customer calls
  • Automatically diagnose “SMS not working” issues
  • Display provider status in our dashboard
  • Prevent unnecessary support loops and escalations
  • Make programmatic decisions based on actual provider state

Without this, we are completely blind to the most critical part of the SMS setup.

🚨 Why Should This Be Prioritized?

This is severely impacting marketplace providers and creating unnecessary support load.

  • We cannot debug customer issues without asking for screenshots
  • Customers get stuck in long support loops because we cannot verify provider state
  • This directly affects customers using custom SMS providers
  • This prevents reliable diagnostics and automation in marketplace apps
  • This is a very common support scenario for SMS integrations

This blocks us from providing a reliable, scalable SMS provider experience

🧠 Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bug-missing-api-fieldSomething isn't working in the Highlevel API or fields are missing in the API Endpoints.lc-phone-smsprocessed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions