[Bug Report] Get Conversation Channels - lowercase SMS results in silent zero results

[i-am-rad]

🐛 Describe the Bug

I queried the API and got nothing back. I used:

https://services.leadconnectorhq.com/locations/hU4UCowz0vcJkuqQxPEd/conversationChannels/sms

{
"conversationChannel": {
"_id": "default_data",
"Email": [],
"defaults": null,
"locationId": "hU4UCowz0vcJkuqQxPEd",
"SMS": []
},
"traceId": "00d1cacd-1b9f-416c-82a4-010515f503ac"
}

I then used capitalized SMS:

https://services.leadconnectorhq.com/locations/hU4UCowz0vcJkuqQxPEd/conversationChannels/SMS

And this returned a proper result.

📍 API Endpoint

/locations/:locationId/conversationChannels/:type

✅ Expected Behavior

Uppercase the path to support any casing received of SMS or sms.

💻 Screenshots or Code Samples

No response

Product Area

conversations

📋 Use Case

bug

🚨 Why Should This Be Prioritized?

bug

🧠 Additional Context

No response

[github-actions]

✅ Issue processed successfully!

Your issue has been reviewed and assigned to the appropriate team.

[Ragavendarb]

Hi @i-am-rad ,
We have added the required checks for the mentioned API - /locations/hU4UCowz0vcJkuqQxPEd/conversationChannels/sms.

Now providing 'SMS' or 'Email' as type - would return the data as expected before.
Whereas providing types like 'sms' or 'email' with case mismatch would throw a 422 error in the response.