@Vapi Hi Vapi team – I need a concurrency counter reset and a valid private API key. Issue: - Outbound campaigns stuck in "Queued" (zero active calls). - Already tried: logging out/in, new campaign with only 5 numbers. - Received the "Concurrency limit hit" email. API Key problem: - My dashboard shows Private API Keys as UUIDs (e.g.,

344480c4-...

). - Calling

GET /org

returns 401: "Invalid Key... you may be using private vs public key". - I cannot fetch my concurrency status because the keys are rejected. What I need: 1. Manual reset of my concurrency counter (Org ID:

18499e31-bed2-47b0-b95f-cf43fdf224e3

). 2. A working Private API Key in

vapi_sk_

format (not UUID). Please advise. Happy to join office hours if needed.

To resolve your API key issue: Try generating a new private API key from the Vapi Dashboard by navigating to Settings → API Keys and clicking Create Key. Make sure the new key starts with `vapi_sk_`—if it still shows as a UUID, contact Vapi support directly for manual intervention. Once you have a valid key, you can check your concurrency status or retry your API calls. [More on API key management](https://docs.vapi.ai/cli/auth) Source: - [Authentication management](https://docs.vapi.ai/cli/auth)

Thanks for getting back to me. As mentioned, I've already tried generating new private API keys from the Settings → API Keys page, but the "private keys" I see in the dashboard (e.g., 344480c4-cf0... and bed14227-b5f...) are in UUID format, not vapi_sk_ format. When I use these, I get a 401 - Invalid Key error. It seems the dashboard is displaying the key ID, not the actual secret. On top of the key issue, my concurrency counter is stuck. Campaigns remain queued with no calls starting, and the system still thinks I'm at the concurrency limit even with zero active calls. This appears to be a known bug. Could you please help by: Manually resetting the concurrency counter for my organization. My Org ID is 18499e31-bed2-47b0-b95f-cf43fdf224e3. Providing a valid private API key that starts with vapi_sk_ (or telling me how to generate it), as the keys currently shown in my dashboard don't work for API authentication. Thank you.

Hey, Can you check it? should be fixed now

Hi Vapi team – my issue is not fixed. Here's the current state: 1. Concurrency still stuck – campaigns remain "Queued" with zero active calls, even after trying new campaigns with 5 contacts. Org ID:

18499e31-bed2-47b0-b95f-cf43fdf224e3

. Please manually reset my concurrency counter. 2. Telnyx integration is connected but outbound calls never start – I have

+18169553113

imported with Telnyx, Outbound Voice Profile active, North America allowed. When I use the "Test Outbound Call" feature in Vapi, it says "Outbound Call Queue Successfully" but the call never rings or connects – it just stays queued forever. 3. Telnyx itself works – I successfully made a call from the same number using Telnyx's own Web Dialer. So the problem is Vapi's Telnyx connector, not my Telnyx config. 4. API keys are UUIDs and return 401 – both my private keys are UUID format, not

vapi_sk_

. Calling

/org

gives "Invalid Key". I cannot debug via API. What I need: - Manual concurrency reset - A valid private API key (starts with

vapi_sk_

) - Investigation into why Vapi's Telnyx integration fails to actually place calls Please advise. Happy to screenshare or provide logs. @Vapi