API Keys

To make setup with Zapier, and other connections via API Key, easier down the line we've added the ability to generate and store Levitate API Keys!

Note: To generate an API key, the Public API feature first must be enabled by your Success Specialist or Support.

There are two kinds of API keys, and which one you need depends on what you are connecting:

Zapier API Keys — account-level keys used for your Zapier connection. They are managed by account Admins, and any Admin can see and manage them. They do not expire.
Personal API Keys — keys scoped to your individual user, used to call the Levitate Public API. Any user can generate one, and you only see the keys you created. These are created with an expiration date and must be replaced when they lapse.

Zapier API Keys

Once the feature is enabled, API Keys can be accessed by account Admins by clicking into the dropdown menu under your name in the upper right corner and choosing Integrations.

Then, you will choose Manage Keys on the API Keys integration card

From there, you'll click on the Generate New Key button, in the upper right corner

Finally, you'll name the API Key you've generated.

To use your API Key, simply choose Copy to Clipboard and paste it in the Zap setup step for Levitate.

Personal API Keys

Personal API keys are scoped to your individual user account rather than your organization, and they are what you use to call the Levitate Public API. Unlike the account-level Zapier keys above, personal keys are created and managed by you: any user on the account can generate one regardless of admin status, and you only see and manage the keys you personally created.

Generating a personal API key

From the same Integrations page, find the Personal API Keys card and choose Manage Keys. Click Generate New Key in the upper right corner, then set the following:

Name — a label so you can identify the key later.
Scopes — what the key is allowed to reach. At least one scope is required. See the Levitate Public API article for what each scope covers.
Expiration — how long the key stays valid: 30, 90, 180, or 365 days. An expiration is required, and there is no never-expires option.

Choose Copy to Clipboard to copy your key and store it somewhere safe.

Key expiration

Every personal API key stops working on its expiration date. After that, requests using it fail with an authorization error that names the date the key expired, and whatever you built on that key stops running until you replace it.

An existing key can't be renewed or extended. To keep an integration working, generate a replacement key before the old one expires, update your script or tool to use the new value, and then delete the expired key.

Note: Set yourself a calendar reminder a week or two ahead of the expiration date. An expired key is the most common reason an integration that had been working suddenly starts failing.

Revoking a personal API key

Return to the Personal API Keys card, locate the key, and delete it. Revoking takes effect immediately, and it has no effect on your organization's Zapier keys or on keys created by other users.

API Documentation

Reference documentation for the Public API — every available endpoint, its parameters, and example responses — is published at api.levitate.ai/docs. The page includes a built-in authorization panel you can use to generate a token in the browser and try an endpoint without configuring anything in your own tooling.

For an overview of what the Public API covers and how to authenticate, see the Levitate Public API article.

FAQs

Q: Can I use my Zapier API key on a platform other than Zapier?

A: No. The account-level keys on the Zapier card are built to work only with a Zapier connection. To call the Levitate Public API from a script or another tool, generate a Personal API Key instead.

Q: Do I need to be an admin to generate a personal API key?

A: No. Any user on the account can generate a personal key. Zapier keys, by contrast, can only be managed by account Admins.

Q: What happens if my key is exposed?

A: Delete the key immediately and generate a new one. Deleting takes effect right away, and any request still using the old key will fail with an authorization error.

Q: Do personal API keys expire?

A: Yes. Every personal key is created with an expiration of 30, 90, 180, or 365 days, and there is no option to create one that never expires. Zapier keys behave differently — they never expire and carry no scopes. See Key expiration for how to replace a personal key before it lapses.

Q: My integration stopped working and nothing changed on my end. What happened?

A: Check the expiration date on the key it uses — a lapsed key is the most common cause. The error confirms it and names the date, reading This API key expired on 2026-08-11. Generate a new API key to continue. Create a replacement key, update your script or tool with the new value, and delete the old one.

Q: Can I extend or renew an existing key?

A: No. Expiration is set when the key is generated and can't be changed afterward. Generate a replacement key instead, switch your integration over to it, and then delete the expired one.