2026-05-28 - Session and API Call Stability Improvements¶
Release¶
AgileData.io - Steadier Sessions: Authentication and API Call Reliability Fixes
A series of targeted fixes have been applied to the way AgileData handles session expiry detection and API call routing in the frontend. These changes address edge cases where expired sessions weren’t being caught early enough, leading to CORS errors or confusing failure messages instead of a clear re-login prompt.
Every API call in the frontend now runs a session expiry check before attempting the request. This means that if your session has lapsed, you’ll be told immediately with a clean re-authentication prompt, rather than seeing an unexpected network error. A number of API endpoint path issues — including trailing slash inconsistencies across catalog fetch calls and data-match patterns — were also corrected to ensure requests reach the right endpoints reliably.
What was happening:
Session expiry wasn’t being detected before some API calls, causing CORS errors to surface instead
Several catalog and data-match API calls used inconsistent trailing slash patterns, causing routing failures
Manual redirect logic on all API calls was interfering with session state management
What this means for you:
Cleaner re-login prompts when your session expires, instead of confusing network errors
More reliable API calls across catalog search, data-match, and other key workflows
Fewer unexplained failures during normal use
Last Refreshed¶
Doc Refreshed: 2026-05-28