Skip to main content

Interested in this feature? Get in touch with your Customer Success Manager.
Session continuation lets Junction recover an App Embed session when no compatible session exists, such as after prolonged inactivity or when using Fast Launch. Your session continuation URL must be a publicly accessible endpoint controlled by your application. Junction redirects the user’s browser to this endpoint with launch parameters. Your application validates the current signed-in user, creates a Junction dashboard URL, and returns a 307 Temporary Redirect to that URL.

Requirements

Your endpoint must:
  • validate that the browser has a valid session with your application;
  • verify that the requested integration member and team match the signed-in user and account context;
  • validate the requested modality, feature, and environment before forwarding them to Junction;
  • create a dashboard URL through the Junction Management API; and
  • respond with a 307 Temporary Redirect to the returned post-authorization URL.
Do not blindly forward query parameters into the Management API. Treat session continuation requests as untrusted input and authorize them against your application’s current session.

Continuation flow

Example endpoint

Redirect status

Use 307 Temporary Redirect so the browser follows the continuation result without treating it as a permanent redirect. This keeps future session recovery requests pointed at your session continuation URL.