Skip to main content
To use the Kimp360 Zapier integration, each user must provide their own API key from the Kimp360 dashboard when setting up a Zap. This API key uniquely identifies you and authorizes your Zap to access your Kimp360 account. Follow the steps below to obtain and use your API key securely.

​
Overview

The Kimp360 Zapier App uses user-specific API Keys for authentication. Every Zap you create that interacts with Kimp360 requires you to enter your personal API key. Requests made without a valid key, or with an improperly formatted key, will result in an authentication error.
An API key is a unique string that identifies and authorizes you (or your application) to access the Kimp360 API. Treat it like a password—keep it secure and never share it.

​
How to Get Your API Key

1

Log in to Your Kimp360 Dashboard

Sign in to your Kimp360 account and from sidebar click on My Account > Settings and then click on Zapier Integration tab. Kimp360 API key page
2

Generate or Locate Your API Key

In the Zapier Integration tab, you can generate a new API key or view your existing key. If generating a new key, you may be asked to name it for easy identification (e.g., “Zapier Integration”).
3

Copy and Store Your Key Securely

Once your API key is shown, copy it. Store it in a secure location, such as a password manager.
IMPORTANT: Keep Your Key Safe!
Your API key gives access to your Kimp360 data. Never share it, embed it in client-side code, or commit it to version control. Do not share your keys with other users.
4

Enter Your API Key in Zapier

When setting up your Zap, Zapier will prompt you to enter your Kimp360 API key when clicked on Account field on Setup tab to authenticate. Paste your personal API key into the authentication field. Each user must use their own key—do not share keys between users. Zapier Auth UI

​
🛡️ Security Best Practices for API Keys

Proper management of your API keys is critical for the security of your integration and data.

Keep Keys Confidential

Treat your API keys like passwords. Do not embed them in publicly accessible code, such as client-side JavaScript or mobile apps that can be decompiled.

Rotate Keys Regularly

Periodically regenerate your API keys, especially if you suspect a key might have been compromised.