After logging into Floot via the magic link sent to your email, your browser holds a signed session token. Push44 asks you to copy this value from your browser's developer tools once, then reuses it for exports until it expires.
📖 Introduction
Floot doesn't expose a public API token in its settings UI, so Push44 authenticates using your active browser session instead. This guide shows exactly how to retrieve that session value.
The Problem with Walled Gardens
Because Floot only supports magic-link email authentication (no password, no visible API token), first-time users aren't sure how to give Push44 access to their account.
The Push44 Solution
After logging into Floot via the magic link sent to your email, your browser holds a signed session token. Push44 asks you to copy this value from your browser's developer tools once, then reuses it for exports until it expires.
Step-by-Step Walkthrough
4 stepsLog into Floot
Go to floot.com and enter your email to receive a magic link. Click the link in your inbox to complete login.
Open browser developer tools
Once logged in, press F12 (or Cmd+Option+I on Mac) to open developer tools, then go to the Application (Chrome) or Storage (Firefox) tab.
Find the session cookie or token
Look under Cookies for floot.com and find the session token value as instructed in Push44's connection screen.
Paste into Push44
Copy the full token value and paste it into Push44's Floot token field. Push44 validates it immediately by fetching your workspace list.
Pro Recommendations
Session tokens expire after a period of inactivity — if Push44 suddenly can't connect, repeat this process to get a fresh token.
Never share this token publicly — it grants the same access as being logged into your Floot account.
Common Pitfalls to Avoid
Copying only part of the token value — session tokens (JWTs) are long and easy to truncate accidentally.
Using an expired token from a previous session.
Frequently Asked Questions
Why doesn't Floot have a simple API key like other platforms?
Floot currently has no public developer API — Push44 works around this using your authenticated browser session, the same way your own browser talks to Floot.
Is it safe to use my Floot session token in Push44?
Yes. It's stored only in your browser's localStorage and used solely to call Floot's API directly from your browser to read your project files.
Export and push your code in seconds.
Connect your platform, preview the visual diff, and create atomic commits on GitHub with zero server data retention.