API keys
Create the key that lets Zapier and Make act on your PageFork team, and revoke it when you no longer need it.
An API key is a password for apps. The PageFork apps on Zapier and Make use one to prove they are allowed to read your sites and forms, listen for new leads, and create leads for you.
You only need a key if you use Zapier or Make. Every other destination is set up inside PageFork and needs no key.
API keys are part of the Pro plan: the things a key can do all require a Pro site. See Basic and Pro plans.
Creating a key
- Open the Team page.
- Find API keys and click Create key.
- Give it a name that says where it will be used, such as “Zapier” or “Make”.
- Click Create.
- Copy the key now. It starts with
pfk_and is shown exactly once. PageFork stores only a scrambled fingerprint of it, so nobody, including PageFork, can show it to you again. - Paste it into Zapier or Make when it asks for your PageFork API key.
Lost the key before pasting it? Revoke it and create another. It takes ten seconds.
Who can create keys
Team owners and admins. Members can’t see or create keys.
What a key can do
A key acts for your whole team, across all of its sites. With it, an app can:
- See the names of your sites, their forms, their custom fields and their pipeline stages, so it can offer them in dropdowns.
- Subscribe to new form submissions and lead stage changes.
- Create leads.
- Look up a lead by its id.
A key cannot log in to PageFork, change your site, edit or delete leads, change billing, or manage your team.
Treat it like a password anyway. Anyone holding it can add leads to your pipeline and receive your new submissions.
One key per tool
Create a separate key for each tool. The list shows each key’s name, its first characters, when it was created and when it was last used, so with one key per tool you can tell at a glance which connection is active, and you can switch one off without breaking the other.
A team can have up to 5 keys.
Revoking a key
- On the Team page, find the key under API keys.
- Click Revoke and confirm.
Revoking takes effect immediately:
- The key stops working. Any Zap or scenario using it fails until you give it a new key.
- Every connection that key created is removed. The “Managed by Zapier” and “Managed by Make” entries under your site’s destinations disappear, and PageFork stops sending leads to those Zaps and scenarios.
To reconnect afterwards, create a new key, paste it into the tool, and switch your Zaps or scenarios off and on again so they subscribe afresh.
When a key stops working by itself
A key belongs to the person who created it. If that person leaves the team, or is no longer an owner or admin, their keys stop working. Have a current owner or admin create a replacement.
Keeping keys safe
- Paste a key only into the official PageFork app on Zapier or Make.
- Don’t put keys in emails, chat messages, screenshots or documents.
- If a key might have been seen by someone it shouldn’t, revoke it and create a new one. There is no downside to rotating.
Troubleshooting
The tool says “Invalid API key”. The key was revoked, mistyped, or its creator left the team. Create a new key and reconnect.
The tool shows a “pro_required” error. The site you picked is on Basic. Zapier and Make need a Pro site.
The tool says too many requests. A key is limited to a generous number of requests per minute. A Zap or scenario stuck in a loop can hit it. It clears by itself within a minute once the loop stops.
“Maximum of 5 API keys”. Revoke a key you no longer use.