First of all, I wanted to say how happy we were to see the barge in endpoints that have been added to the conversations API!
Exploring those, we found that the /api/v2/conversations/calls/{conversationId}/participants/{participantId}/barge endpoint works great, but the more generic /api/v2/conversations/{conversationId}/barge always returns us a 404. We have tried both the developer center's execution of the API and tried it in code using the .NET SDK. The generic version would suit our purposes more easily, but we are able to make the participant version work. If it is an us problem, I would love to have some help figuring out what the issue is, but in case it is not, I wanted to make someone aware.
Thanks!