Manage API Keys Efficiently In Vapi Dashboard

Quick but important bit of background. Vapi gives you two kinds of keys, and the difference really matters. Your Private key is for server-side use and has full access, so you guard it like a password. Your Public key is for client-side and SDK use, which means it's safe to drop into browser or app code. Mix those up and you can either break your integration or leak something you shouldn't. So let's go find both and copy them the right way.

Written By Fred

Last updated 3 days ago

Go to dashboard.vapi.ai

1. Introduction

First, head to dashboard dot vapi dot ai and sign in. You'll land on your main dashboard. This is home base for building assistants, managing phone numbers, and a lot more. But today we're after your keys, so let's go straight to them.

Introduction

2. Access API Keys Section

Look at the bottom of the left menu, under the "MANAGE" heading, and click "API Keys." That opens the page where both of your keys are listed and ready to copy.

Access API Keys Section

3. Initiate API Key Creation

Click here to start creating a new API key within the dashboard interface.At the top you'll see your Private API Key, marked for server-side access. This is the powerful one with full access, so it belongs only in your backend, never in code a visitor could see. Click the copy icon on the right to grab it, then paste it somewhere secure like a password manager or a server environment variable.

Initiate API Key Creation

4. Confirm API Key Setup

Now scroll down to your Public API Key, marked for client-side and SDK access. This is the one that's safe to use in browser or mobile code, since it's limited by the domain and assistant rules you set right below it. Click its copy icon to grab it for your front-end integration.

Confirm API Key Setup

And that's it. You've opened the API Keys section and copied both of your keys: the Private one for your server, kept secret, and the Public one for your client-side code. You're all set to start wiring Vapi into your apps and building voice agents. Happy building, and I'll catch you in the next one.