[Bug] Add Inbound Message - 500 Errors

[i-am-rad]

🐛 Describe the Bug

If you supply the wrong conversationProviderId you get a 500 instead of a 400 and detailed error.

📍 Location

Which page/endpoint does this relate to?
https://marketplace.gohighlevel.com/docs/ghl/conversations/add-an-inbound-message

✅ Expected Behavior

What should have happened?
-Return a 400 with incorrect or nonexistent conversationProviderId

💻 Screenshots or Code Samples

{
"type": "Custom",
"conversationId": "B3ZIjGFwjGdtUHJBGoYE",
"conversationProviderId": "i plugged a locationId in here by accident which gave the 500",
"html": "test",
"subject": "test",
"emailFrom": "redacted",
"emailTo": "redacted",
"altId": "myaltidsample",
"direction": "outbound",
"date": "2025-05-19T14:24:14-04:00"
}

🧠 Additional Context

[gauravkanted-ghl]

@ravi-des @swagata-c Let's fix this at the earliest please.
cc: @karanagarwal17

[i-am-rad]

Got another one. Same endpoint. If you pass an incorrect auth token it returns:

{
"statusCode": 500,
"message": "Internal server error"
}

[i-am-rad]

And the voicemail player for Call providers is no longer displaying for inbound voice messages. (RESOLVED)

[i-am-rad]

Additional bug. If you fail to supply "emailTo" then it gives back bugs on custom email providers instead of specific feedback ona. missing field.

Error in GHLAddInboundMessage: Error: Failed to parse API response: {"success":false,"message":"Cannot read properties of undefined (reading 'split')","traceId":"213c9c33-68a3-4e02-9b7f-7a5367ad7d45"}

Payload I sent (redacted):

{
  "conversationId": "test",
  "type": "Custom",
  "direction": "inbound",
  "conversationProviderId": "681cd8a3fe547f0fa3069224",
  "emailMessageId": "test",
  "altId": "test",
  "emailFrom": "test@test.com",
  "subject": "chat",
  "html": "test"
}

[i-am-rad]

Going to just keep adding things here for add inbound message. Call providers "from" and "to" are easy to mess up. They need to have better error messages. If the contact does not exist the API call fails and error messages not detailed enough to explain why. Suggested error message: "Contact does not exist." or something standardized.

[i-am-rad]

If you pass the date field in an incorrect format or date in the future the api returns, "[401] The token in Authorization header is not valid!"

This was on type Custom email providers.

[balaji-ghl]

@i-am-rad The following issues have been fixed:

1. Returning a 500 status code instead of 400 for invalid conversationProviderId.

2. Returning a 500 status code instead of 400 for invalid emailTo values or when the field is missing.

[i-am-rad]

Any update on the passing of incorrect date? You guys need to really look in the code base what is causing 401 errors like that one. Ive seen it elsewhere when data validation is failing.

[balaji-ghl]

@i-am-rad We had already picked this up and completed it before the reported date issue. Could you please raise a separate issue specifically for that date? It’ll be easier to track. We also recommend keeping one issue per report to make it easier to follow.