Skip to main content
Your API key is the password a piece of software uses to talk to Liftify on your account’s behalf. You need it if you or a developer are pulling Liftify data into another system, or pushing data in. If nobody is writing code against Liftify, you can ignore this page entirely.

Find the key

  1. In the left sidebar, click the circle with your initials, then Settings.
  2. Under Integrations, click API Keys.
The page is headed API Access and explains: “Use this API key to authenticate API requests for this account.” The key is hidden by default — you see only the first and last few characters. Use the buttons beside it:
  • Show reveals the full key. It turns into Hide once revealed.
  • Copy puts the key on your clipboard without revealing it on screen.
Below that, the page shows the line a developer needs to send with every request, starting Authorization: Bearer. Its own Copy button copies that whole line, ready to paste.
Anyone holding this key can read and change your account’s data through the API. Treat it like a password: never paste it into a chat message, a shared document, or an email. Hand it to a developer through whatever secure method you would use for a password.
The key hides itself again as soon as you navigate away, so it is not left sitting on screen.

Check whether API access is on

Beside API Access Status you will see one of two labels:
  • Enabled — the API is switched on for this account and the key will work.
  • Not Enabled — requests will not go through, even with the right key.
You cannot switch this on or off yourself. The page says it plainly: to enable or disable API access for your account, contact support@liftify.com. Ask before your developer starts work, so they are not debugging a connection that was never turned on.
Support also handles anything else key-related — if you believe the key has leaked, email them.

What to do with it

Give the key and the Authorization: Bearer line to whoever is building the connection. Everything else they need — the addresses to call and the data they return — is in the API documentation, reachable from the button at the bottom of the page: View API documentation, at docs.liftify.com.
The API Keys entry appears in settings only for users whose permissions cover it. If you do not see it, ask an administrator on your account, or contact support.

Make a narrower key instead

The account key above reads and writes everything on the account. If you are handing access to a contractor, a reporting tool, or anything you would rather not trust with the whole account, make an API client instead: a named key you can limit to particular locations and to reading only. The API Clients card sits below the account key, described as: “Named API keys that can be limited to specific locations and to read-only access. Keys are fixed after creation — to change locations or scope, create a new key and deactivate the old one.”

Create one

Under Create API client: Click Create API client. It appears in the list above with its own key, masked, with the same Show and Copy buttons as the account key.
A key’s name, access level, locations and expiry are fixed once it is created — there is nothing to edit. If any of them need to change, create a new key and deactivate the old one.

Read the list

Each key in the list carries badges telling you what it is and where it stands: Underneath, a line names the locations it covers — or All locations — plus its expiry date and when it was last used, when Liftify has those. Last used is the quickest way to find a key nobody needs any more.

Switch one off

Click Deactivate beside a key and it stops working immediately. The button becomes Activate if you need it back. Deactivating is the right response to a key that has leaked, or to an integration you have retired — there is no delete.
If your own access is restricted to particular locations, you do not see the account key at all, and every key you create must name at least one of your locations: “Select at least one location. Keys you create are limited to your assigned locations.” A narrower user cannot mint a wider key.