LighthouseMike | 2023-01-20 01:05:50 UTC | #1
Ran into the same problem as this guy.. Code is pretty much identical. Like him my only hypothesis is that it might be something about the participant ID. I've tried what I think is my ID (a session's pcParticipant.id, and also the ID obtained from foo.bar.baz.lol.getUsersMe or whatever it is :laughing: ). I've tried calling conversations.getConversation and sifting through the list of "participants" to find the one marked "customer" and tried the "id" from that... I've also tried "Digits" with a capital D, since that's how it is in the docs. Nope. 400. I'm baaaaaaaad. :laughing: Unfortunately, all the docs say is "participantId", and the message of my 400 is just "Bad Request". May as well be "Kiss My Bits. You Dare Challenge Me, Puny Human!" :laughing: Any clues on what a "good" request looks like? Maybe it requires a user ID now after all? :laughing: Sorry, I'm hitting all the glitchy edge cases tonight.
EDIT: I discovered the issue through extensive trial and error. Here's how I depuzzled it, in case anyone else finds themselves in this situation:
- even though the docs say "digits", it's really "digit" - as in ONE DIGIT. NO MORE. This is probably why the GUI has one of those funky dial pad widgets instead of a simple
<input type="number"/> lol - Also, in my current code, I used the pcParticipant.id - I knew enough variations on my experiment would eventually lead to a valid participant ID. Wish the docs would have just told me who's participant ID, but I got there.
- Also, it's "digits" lowercase
John_Carnell | 2023-02-07 13:29:58 UTC | #2
This post was migrated from the old Developer Forum.
ref: 18068