Update on Session Token Expiry Date Change
This change has for now been reverted, and the previous functionality is currently restored.
While this update is not in effect right now, it will be re-implemented in the near future. However, at this time, we do not have a specific release date.
We appreciate your patience and understanding as we work towards implementing this change effectively. Please stay tuned for further announcements regarding its deployment. As always, if you have any questions or need assistance, our support team is here to help.
Thank you for your continued support.
We have recently updated our API to enhance security and ensure optimal performance. Session tokens can now only be created with an expiry date set to a maximum of 6 months in the future. If you attempt to set an expiry date beyond this limit, our API will return the following message:
“Expiration date is not allowed to be older than 6 months.”
This change is reflected in our latest changelog, where we detail the additional validation added to the token/session/:create method.
We encourage you to review your applications and ensure that they align with this update to avoid any disruptions. If you have any questions or need further assistance, feel free to reach out to our support team.
Thank you for your understanding and cooperation.