The documentation for CRM/WebLogins/Search says that both emailAddress and loginTypeId are not required, however they both appear to be required.
also the search seems to fail if the email address has a plus (+) symbol in it.
"+" is a common character for customers using google for email. Either Gmail or an organizational domain hosted by google.
I've run into other REST API calls that seem not to have the required fields listed clearly.
Hi
Do make sure to send in a support ticket to hello@tessituranetwork.com when you find the documentation around fields incorrect - it's possible it's been fixed already in a more recent service pack but it's always good to check with us to find out.
Alan Draper those two parameters have been updated in the most recent service pack - I recognize that is not immediately helpful if you are working with a previous version or service pack - please continue to send up support tickets when you find that API docs don't accurately reflect field information or other details.
CC Patrick FitzGerald
Regarding email addresses with a plus symbol: This is commonly used to "fake" having an extra email address, but still have the email go to the same account. It only works with some mail servers, google being one of them. So for example you could email simon+testing@redcrowdigital.com.au , and the email will still be delivered to simon@redcrowdigital.com.au. It doesn't matter what you put after the plus symbol, so you therefore have an endless supply of email addresses to test with.To search for these addresses in the Tessitura API and other systems, you often need to URL encode the email address string first. Different programming languages will have different ways of doing this, but the result will be the same. Characters like the plus symbol are replaced with equivalents that can safely be sent in a URL query string. For example try this:https://www.urlencoder.org/
...and note that if you enter in simon+testing@redcrowdigital.com.au , it is encoded to simon%2Btesting%40redcrowdigital.com.au , which would then be valid for adding to a URL query string.
Yes. That's what I did, used System.Net.WebUtility.UrlEncode(username).
But when you're consuming an SDK, you aren't thinking about query strings. In fact it is opaque whether the SDK puts the values in a querystring (like WebLogins/Search) or in the body of a post (like TXN/Performances/Search).
Either the SDK documentation should be changed to indicate that the search parameters should be url encoded, or the SDK should be changed to URL encode the parameters before sending.
Hi Alan Draper - We took a look and for that request, agree that the SDK should be doing the URL encoding. We'll file it as a defect. Thanks for bringing it forward.
Chris