I've noticed a new unsupported optional feature called "Disable sessions for REST API". Can anyyone tell me what this does please? I'm wondering if it's designed to prevent an issue where regular API calls can cause it to fail due to too many existing sessions?
If that checkbox is used it should ask for authorisation on every call.
Without it (the default way) you authorise only on first time and then you have a session open until it expires.
Marking forum post as closed now as we have not received further response.
If you have any issues or questions you wish to discuss on this please open a new post.
Thank you in advance.
I've found an issue which I'm trying to find the best way to resolve.
An integrated proof of delivery system sends two pieces of data to the SERP API, in two separate calls - let's c...
There are some topics in this Q&A related to this question, but none of them is about Idle users - Concurrent or Named.
If timeout minutes are specified in Optional Features, then all idle users are...
