Skip to content

[Bug Report: Documentation Errors] #106

@yotomations

Description

@yotomations

🐛 Describe the Bug

I created a custom conversation provider via a GHL plugin. When I try to call it it using a private Integration key scoped to a sub-account, I get:
You don't have access to the conversationProvider with id: <myConvProviderId>

I'm using the https://services.leadconnectorhq.com/conversations/messages/inbound endpoint with this payload (Which works great when i don't specify a conversationProviderId)

{
  "type": "Custom",
  "message": "Any Message,
  "conversationId": "<The right Conversation ID>",
  "conversationProviderId": "<myConvProviderId>",
  "altId": "<AnyAltID>",
  "direction": "inbound",
  "date": "2025-07-31T19:40:07.843-04:00"
}

Am I missing something or is this a bug?

📍 API Endpoint

https://services.leadconnectorhq.com/conversations/messages/inbound

✅ Expected Behavior

A messasge should be posted to under conversation provider

💻 Screenshots or Code Samples

No response

Product Area

ad-publishing

🧠 Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions