An API Key is a credential on your ImageToTable.ai account. It lets an outside tool act as your account: the Google Sheets add-on can connect with it instead of signing in, and the v1 API uses it on every call. This page covers where the key lives, how to replace it, and what to update once you have.
Where to find your API Key
The key is on your Profile page, in a section titled API Key. To get there, open the account menu in the top-right corner of the app — the one with your avatar and username — and choose Profile.
That section shows everything the key needs:
- The key itself, hidden behind dots by default. Use the eye button to reveal it, and the Copy button to copy it.
- A button that reads Regenerate API Key when a key already exists, or Generate API Key when there is none yet (the section shows No API key yet in that case).
- A short note that the key is for external tools, with a reminder to keep it secret, plus a link to the API documentation.
Treat the key like a password. It belongs to the account rather than to any single tool, so the same value works everywhere a key is accepted — and anyone who has it can act as your account. That is the reason the section tells you to keep it secret.
Regenerating your API Key
An account holds a single API Key. Regenerate replaces that value rather than adding a second key, so there is never more than one active key. The confirmation step depends on how your account signs in, because an account created with Google sign-in has no password you would know to type here.
If your account signs in with a password
Choosing Regenerate API Key opens a password prompt. When a key already exists, the prompt states that the current key will be invalidated before it asks for your password; when there is no key yet, it asks for your password to create one. Enter your account password and confirm to finish.
If the password does not match, nothing changes and the page reports that the password was incorrect.
If your account is linked to Google sign-in
For an account that signs in with Google, the confirmation is a Google sign-in step instead of a password. Choosing Regenerate API Key opens a dialog titled Confirm your identity, which asks you to confirm through Google. If the account already has a key, the dialog notes that the current key will be invalidated first.
This is the path to use when the password prompt above is not an option for you, which is the case for accounts created through Google sign-in.
After regenerating: update the places that use the key
Generating a new key takes effect immediately. The previous value stops working at that moment — there is no grace period and no way to keep both keys active. Anything still sending the old key is refused until it is given the new one.
| Where the key is used | What to do after regenerating |
|---|---|
| Google Sheets add-on | Open the Account section in the sidebar and paste the new key into the Paste API Key box. If the add-on is connected with Sign in with Google instead, it does not use the key at all and needs no change. |
| v1 API | Replace the old key with the new one everywhere your application stores it. Calls made with the old key no longer authenticate, so update the key before your next run. |
Regenerating changes only the key. Your files, templates, credits, and plan are untouched, and the new key carries the same access as the old one.
Common questions
I lost my key. Can I look it up again?
Yes, as long as you can sign in. The Profile page always shows the current key; it is hidden behind dots until you reveal it with the eye button, and you can copy it from there. If you would rather replace it than reuse it, use Regenerate API Key instead.
Can I have more than one key at a time?
No. The account holds one API Key. Regenerating replaces it, so the previous value stops working as soon as the new one is generated.
Does the Google Sheets add-on always need a key?
No. The add-on can connect either by signing in with Google or by pasting an API Key. If you connect it with Google sign-in, the sidebar does not use the key, and regenerating a key does not affect that connection. Only the places using the key itself need updating. See Google Sheets Add-on.
Does the v1 API use this key?
Yes. Every v1 API call authenticates with the key, which is why the old one has to be swapped out after regenerating. API Access covers who the API is for and what it requires; the full reference is on the developer documentation site.