@OmarAlmonte, need to point out a new error that was raised via the Tags - Create Tag endpoint.
Tag name is invalid. Details: Cannot contain '=' or ',' characters.
In the XML-RPC API this was not an issue. it would be better to either escape or filter out those characters on your end and not force to deal with it on the integration end.
Also, the documentation does not mention anything about those limitations.
Hi @Pav, thanks for pointing this out.
We’ll look into this. A validation was explicitly added in the REST v2 implementation that prevents tag names containing = or ,, which explains the behavior you’re seeing.
You’re also right that this limitation isn’t currently documented. We’ll review both the validation itself and the documentation to determine the best path forward.
The integration is adding Tags from Webinar Names, so the symbols are always expected.
I would have expected commas to be allowed given it is not a non-threatening symbol.
If you use the application, you do get the following warning message below.
Although there is a contradiction between allowing multiple tags with commas and what the message says.
To replicate it, just use the equal sign in the tag name, and save the tag.
