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.
📖 Introduction
Zite (built on the Fillout infrastructure) protects its API with double-token CSRF security, meaning you need both a session cookie and a CSRF token to authenticate. This guide shows where to find both.
The Problem with Walled Gardens
Zite has no public developer settings page for generating an API key, which confuses users trying to connect third-party tools like Push44.
The Push44 Solution
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 Walkthrough
5 stepsLog 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 Recommendations
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 Pitfalls 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.
Frequently Asked Questions
Why does Zite need two separate tokens?
This is a standard CSRF-protection pattern: the session cookie identifies you, and the CSRF token proves the request came from an authorized page, preventing cross-site request forgery.
What exactly does Push44 export from Zite?
Push44 reads your app's full snapshot template — every component, layout, and configuration setting — and pushes it to GitHub as source 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.