How to get my Vapi API key?
# support
m
Hi Vapi team I'm working on integrating Vapi with Make.com to trigger outbound AI calls automatically from Google Sheets. I’ve already set up my assistant and everything is working inside the dashboard. However, I need an API key in the sk-proj-... format to authenticate my requests to the /call endpoint — but I don’t see an option to generate it in my dashboard. I only see a UUID-style key, and the system doesn’t allow me to “upgrade” or enable API access manually (only shows “Add Credits” and “Contact Sales”). Could someone from the team please enable API access for my org or let me know what plan I need to be on or If I need one? Thanks in advance!
v
Hi there! 👋 Thanks for reaching out about integrating Vapi with Make.com. I'd be happy to help you with your API key question. To better assist you, could you please share which subscription plan you're currently on? Based on the information I have, certain API features may require specific plans (like Enterprise) that include higher rate limits and API access. Also, have you tried accessing the Provider Keys section in your dashboard at [dashboard.vapi.ai/keys](https://dashboard.vapi.ai/keys)? This is where provider keys for various services are typically managed, though I understand you mentioned only seeing a UUID-style key. This will help me determine the next steps for getting you the proper API key format you need for the integration. Sources: - [Enterprise Plans Information](https://docs.vapi.ai/enterprise/plans) - [Provider Keys Dashboard](https://dashboard.vapi.ai/keys)
m
Thanks for the quick reply! I’m currently on the Pay As You Go plan — I’ve added credits and set up a fully functional assistant. I’m looking to integrate with Make.com, and I need a server-side API key (sk-proj-...) that works with the /call endpoint to trigger outbound calls programmatically. I’ve checked the Provider Keys section, but the only available key is a UUID-style format (not usable in Authorization headers as expected). Could you please confirm: Whether Pay As You Go accounts can request access to sk-proj-... keys? Or if I need to upgrade to a Starter or Enterprise plan to unlock API capabilities? I’m happy to upgrade if that’s what’s needed — just want to confirm the path. Thanks again! @Vapi Support Bot
v
Thanks for providing those details! I've looked into your question about the sk-proj-... format API keys, but I don't have the complete information about this specific key format and whether it's available on your current Pay As You Go plan. I've escalated your query to our technical team who can provide you with the exact information about: - Whether Pay As You Go accounts can access sk-proj-... format keys - If you need to upgrade to a Starter or Enterprise plan for API access - The exact steps to enable the key format you need for the /call endpoint A team member will get back to you shortly with specific guidance. Based on the information I found, Enterprise plans do include "unlimited concurrency and higher rate limits" for API usage, but I want to make sure you get the precise answer about the sk-proj-... format keys you need. Thanks for your patience! 🙂
m
@User Any help?
s
Hey Moe, Our API keys don't start with'sk-project-following'. These are generally other providers' API key formats. To get the VAPI private API keys, simply visit the following page and then you can copy them from there.
m
So I should use my private key to connect on make.com? would it work?
k
You can
Connect using your API keys
private keys are mainly used for generating JWTs in server to server setups.
m
How do I know if my API key authorized to use the /call endpoint for outbound calls? I'm trying to do it through Make.com but I keep getting Error 400, is it because of the type of the plan? and how to fix this?
k
400 error when /call endpoint via Make.com may be due to plan restrictions free plans may block outbound calls, an invalid API key, ensure you’re using a valid assistant Id, correct phone number format, and consider using the HTTP module with the right JSON structure..