Whop API key: connects but nothing launches
Fix a Whop company API key that connects fine but can't launch, or reports zero spend, because it's missing permissions.
This page is for your own Whop account, connected to Koast with a company API key. If the key connected without complaint but launches fail or spend stays at zero, the key is almost always missing a permission.
WhopWhat you see
One of these:
- The key connects and you can pick your ad account, but every launch fails.
- Campaigns launch and deliver, but every result stays blank: spend, impressions and clicks never fill in.
- An error that names a permission, straight from Whop:
That message comes straight from Whop, and the permission at the end changes with what Koast was trying to do. When Whop doesn't name one, Koast shows this instead:
Why it happens
Whop lets you create a company API key with any set of permissions, even none, and the key still connects. Koast only finds out a permission is missing when it tries to use it, so nothing warns you when you save the key. That's also why a key can launch campaigns and still show no results: reading an ad report needs its own permission, ad_campaign:stats:read. A key without it can create and update campaigns, but Whop refuses every report request, so Koast has nothing to show and every metric stays blank.
Connect your own Whop account lists the 13 permissions Koast uses. Whop adds permissions over time, so ticking everything the key offers is the safest way to avoid this.
How to fix it
In your Whop dashboard, open Developer and create a company API key with every permission ticked.
In Koast, open Settings, then Whop.
Select Replace API Key and paste the new key into Company API key.
Launch again.
Still stuck?
Send us the exact error and tell us which permissions the key has. Still stuck? Message us from the chat bubble.