Skip to main content
Create a profile, sign in during one session, and close that session to save. Later sessions start signed in. Set TILION_API_KEY first.

Save the login

This example creates the profile, opens a session with save: "replace", and prints a live-view URL. Sign in through that URL, then let the script close the session.
X-Tilion-Profile-Save: saved confirms the new version. For any other value, read profile_save from GET /v1/session/{id}/status, which has the reason for an hour after the session ends.

Start signed in

Name the profile on create. The default save is none, so the session reads the profile and leaves it unchanged.
Authentication still depends on the site accepting the restored state. Close each session when finished.
sessionStorage comes back in a new session’s first tab, in every mode. A save reads it only from the site each tab is on at that moment, so if a site keeps its login there, end the session on that site. See What is restored.

Choose a mode

  • Keep the default for a site that needs cookies and page storage.
  • Add "full": true in the profile block when a site also needs its service workers, caches or the same device. The create takes one Chrome launch longer.
  • Use save: "merge" when several sessions write at the same time. With replace, the first session to end saves and later ones lose their changes.
See Browser profiles for what each mode restores, limits, and two sessions on one profile.