If I get a new session key and use it to get login info, it returns the response that is expected (i.e. IsLoggedIn: false, etc). If i use my valid login (same one I am able to use via SOAP), the response is "null" and I get the same thing if get login info on that same session key. Is there something I am doing wrong. I am passing LoginName, Password, SessionKey and LoginType in the body. The response status is 200.
Which login method are you calling in REST? Security/ValidateWebLogin should return the constituent details on authentication. I found that my REST user that we use for API calls didn't have the appropriate access to this function so you may need to update security preferences for your login. Hope that helps
Thanks for the tip. I tried that endpoint and it logs me in, but how does this work with a session key. The /Web/Session/Login endpoint seems similar to the way we did it in the soap api and takes a session key. I assume other endpoints will use that for session specific data.
I am on v12.5 - and i see this under /Web/Login - "The resources and methods under /Web (/Cart, /Login and /Session) are currently reserved for internal use in the Android tablet application, TRBO (Tessitura Roving Box Office), for this version of the Tessitura application platform. These methods and underlying contracts are likely to change as we build out additional REST API functionality, and therefore they are not recommended for active web development. Using them for prototyping and spiking future web solutions is appropriate at this time."
I think I need to upgrade to latest version before building out the session part of my app. i will focus on the Perfs and Packages for now.
Ah yes 12.5 only has partial REST integration from V14 onwards you can do full integration, I'm just about to start the 6 month process of swapping all our SOAP methods to REST. Good luck with your setup.
William, that's great to hear. We are looking for community members who are working through this. You'll definitely want to look at some of the changes in 14.1's API, particularly around customer #0 - there are some basic differences in how you need to handle session state in REST (no more anonymous Tessitura customer needed, for example). It should simplify things a fair bit.
We'd love to hear more from you as you go through this process, so please keep us informed either here or via the slack channel for developers!
Casey Vollmer we'd love to hear from you about your experience developing with REST as well as you build your app.
Chris Szalaj
Hi Chris,Yes I'm enjoying the constituent 0 functionality in 14.1 as well as the LoginAsGuest and search methods. I've just built an Education booking form that searches Tessitura if the customer already exists and if their school exists and if not creates the records, logs them in as a guest, updates data protection and buys their tickets without the need for a lengthy sign up process or creating duplicate records. Bit of an experiment really to see what can be achieved with all the new options.Looks like the documentation for all the new methods at this stage is still a little bare bones, happy to contribute what I learn to help others start using it especially around contact permissions which is already presenting some really creative additional possibilities for data capture and regular reminders for our box office and fundraising teams.ThanksWill