We're looking to offer a passwordless website login via an emailed token. The REST API has a SendCredentials method for generating a credentials email, but the recommendation from Tessitura has been to set email frequency to every 5 minutes. From a UX perspective, a 5 minute wait time (or even the minimum 1 minute) is too long for a purchase path login.
One option to speed this up would be to have the website use its own SMTP server to send a token email instead of TPS. We are able to use CRM/WebLogins/{loginId}/LoginCredentials to retrieve a generated token. However, we found that it stays null until calling SendCredentials, which attempts to send its own email. So we have two questions:
Hi Zachary,
We send emails every 1 minute and haven't found that it impacts Tessitura processing negatively. Results may vary, however. Note that it's not necessarily a full one minute wait. It could kick off immediately or within seconds depending on the request's relation to the queue's timing.
Robert