What could be causing this issue? We have GHL API connected. I also tried the GHL MCP one but we're still getting the error. It was working before. https://cdn.discordapp.com/attachments/1476354807206776996/1476354807349645473/image_30.png?ex=69a0d20f&is=699f808f&hm=4a4fdfe1fef7a5bd141b3eb77db059b4a8a718573056740ceb53a2fa011ac4b9&

The error suggests your GoHighLevel authentication session is missing or expired. To resolve this, reconnect your GoHighLevel account in Vapi: 1. Go to the Vapi Dashboard. 2. Navigate to Providers Keys → Tools Provider → GoHighLevel. 3. Click Connect and follow the authorization prompts. This should refresh your credentials and restore integration functionality. For more details, see the [GoHighLevel integration guide](https://docs.vapi.ai/tools/go-high-level). Source: - [GoHighLevel Integration Guide](https://docs.vapi.ai/tools/go-high-level)

I CAN HELP @Yssa Amper Hey Yssa! That "was working before" GHL API break usually comes down to a silently rotated key or a scope shift after a platform update, just resolved this exact issue for Yantree and West Coast Cowgirl recently. 🚀 Quick questions: What's the exact error? Sub-account or main agency? Drop those and I'll pinpoint the fix instantly! 👋

It's a subaccount. Error is shown in the image attached. I tried creating a new API key and it's still the same.

That error usually happens when: The authentication session expired The API key was revoked or regenerated The Location/Sub-account ID changed MCP isn’t properly initialized before the tool call Missing/invalid access token refresh Since it was working before, it’s most likely an expired session or credential mismatch. @Yssa Amper

@Adam @KENNY Thanks! However, I've checked all of these already. The error is still there.

Hi, This is a known issue, and our team is working on the fix. Meanwhile, you can try the following troubleshooting steps: 1. **API Key Verification**: Double-check that you're using the correct GoHighLevel API key from your sub-account. You can find this under the "Business Info" section of your GHL sub-account. 2. **OAuth Authorization**: Ensure that all required permissions are granted during the OAuth authorization process. You might want to try revoking any existing access and attempt the authorization process again, ensuring all prompts are followed. 3. **Vapi Dashboard Validation**: After reattempting the integration, navigate to the Vapi Dashboard to verify that the status updates. If it still shows "Connect", consider restarting the integration from scratch. 4. **Connection Logs**: Check any console or error logs during the connection attempt for clues as to why it isn't completing successfully. These logs can often point out missing credentials or permission issues. Further investigation may be necessary to check for backend problems, as well as any changes in the integration processes between GHL and Vapi. You can also refer to [GoHighLevel Integration documentation](https://docs.vapi.ai/tools/go-high-level) for additional configuration details.