Hi @owalsdor,
Thanks for your patience so far!
Yes, I believe when you say the Developer Portal interface has been totally changed now, it's actually the Newly revamped Webex Developer Portal to meet certain standards and going ahead, we'll continue with this design definition only for the Webex developer portal.
I think you're referring to this new design as I shared a screenshot -
Now, there has been couple of glitches with the new design of the Developer Portals and our Dev Portal engg. team are working on those glitches with priority.
I think you're getting this error because if you observe the Request parameters fields in the /createa-a-message API, those are already pre-filled with some of the sample values.
And when I say all the request parameter fields, I mean basically all the fields like "toPersonEmail", "roomId", "toPersonId" and even the other fields as well.
Now all these fields I mentioned above, these are the destination where you want to send a message.
Now you can't use these all parameters in a single /createa-a-message API request. You need to use any one of these.
But problem is as I mentioned, all these fields are already pre-filled with some dummy values.
So, you should first clear up all these fields where ever you see these dummy values, basically clear up everything. You should not do it manually actually. There should be just placeholder values, but this needs to be fixed.
For now, after you clear up the values manually - then just provide a roomId or, a personID or, a personEmail where you send the message and your message in the "text" field.
And use your Bearer Token in the Authorization field and you should Run the request.
But I think even after following these instructions, you still might face some unknown error.
Because I tried to test by creating a message and just provided the value in the "text" field and "toPersonEmail", rest of the fields I cleared up manually. Still I'm getting an error.
I tried using a "roomId" as well in the request, but doesn't help either.
And this needs a fix on priority. If you continue to face the same error, please raise a request by sending email to devsupport@webex.com and we'll look at it further.
For the time being, you can try to use this API from POSTMAN as shared a screenshot below and that should work fine.
So, it's not a problem with the API, basically the new developer portal is not processing the request correctly for now.
Regards!
Sandip
Hi @owalsdor,
Thanks for your patience so far!
Yes, I believe when you say the Developer Portal interface has been totally changed now, it's actually the Newly revamped Webex Developer Portal to meet certain standards and going ahead, we'll continue with this design definition only for the Webex developer portal.
I think you're referring to this new design as I shared a screenshot -
Now, there has been couple of glitches with the new design of the Developer Portals and our Dev Portal engg. team are working on those glitches with priority.
I think you're getting this error because if you observe the Request parameters fields in the /createa-a-message API, those are already pre-filled with some of the sample values.
And when I say all the request parameter fields, I mean basically all the fields like "toPersonEmail", "roomId", "toPersonId" and even the other fields as well.
Now all these fields I mentioned above, these are the destination where you want to send a message.
Now you can't use these all parameters in a single /createa-a-message API request. You need to use any one of these.
But problem is as I mentioned, all these fields are already pre-filled with some dummy values.
So, you should first clear up all these fields where ever you see these dummy values, basically clear up everything. You should not do it manually actually. There should be just placeholder values, but this needs to be fixed.
For now, after you clear up the values manually - then just provide a roomId or, a personID or, a personEmail where you send the message and your message in the "text" field.
And use your Bearer Token in the Authorization field and you should Run the request.
But I think even after following these instructions, you still might face some unknown error.
Because I tried to test by creating a message and just provided the value in the "text" field and "toPersonEmail", rest of the fields I cleared up manually. Still I'm getting an error.
I tried using a "roomId" as well in the request, but doesn't help either.
And this needs a fix on priority. If you continue to face the same error, please raise a request by sending email to devsupport@webex.com and we'll look at it further.
For the time being, you can try to use this API from POSTMAN as shared a screenshot below and that should work fine.
So, it's not a problem with the API, basically the new developer portal is not processing the request correctly for now.
Regards!
Sandip
