✅ Quick Summary
Both required values are present in your browser once you're logged into Zite. Push44's connection screen tells you exactly which cookie names to look for.
The Problem
Zite has no public developer settings page for generating an API key, which confuses users trying to connect third-party tools like Push44.
How Push44 Solves It
Both required values are present in your browser once you're logged into Zite. Push44's connection screen tells you exactly which cookie names to look for.
Step-by-Step Guide
Log into your Zite app editor
Go to build.fillout.com and open the Zite app you want to export.
Open developer tools
Press F12 and go to the Application/Storage tab, then Cookies for the Zite domain.
Copy the session ID
Find the session cookie value as labeled in Push44's connection form and copy it exactly.
Copy the CSRF token
Find the CSRF cookie value in the same list and copy it as the second credential.
Paste both into Push44
Enter both values into their respective fields in Push44's Zite connection screen, then continue to select your app.
Pro Tips
- Both tokens are tied to your current login session — if you log out of Zite, you'll need to grab fresh values.
- Keep both values private; together they can authenticate as you on Zite.
Common Mistakes to Avoid
- Mixing up the session ID and CSRF token fields — Push44 needs both in the correct field.
- Copying a stale value from an old browser tab that's since logged out.
Ready to Export?
Push44 is free, open source, and takes under 2 minutes to set up.