Hello all. I was looking through using the Web beta SDK and trying to get it working. When I thought I was using the right API key I keep getting Invalid API key. Use your RevenueCat Billing API key. I have tried all of them that I see and am looking to find where that one is located.
Hi
What’s API key are you using? It should be one of the two public API keys of your RevenueCat Billing App. There are two, one for production (starts with rcb_
) and one for sandbox (starts with rcb_sb_
).

To test that everything works well, you can run this command and you should get a 200 response.
curl https://api.revenuecat.com/rcbilling/v1/branding -H 'Authorization: Bearer <your-api-key>'
If you still have problems you can open a support ticket providing more details about your problem and we will help you solve the issue.
hey
...Actually maybe I figured it out. I think I just need to use the rest API (https://www.revenuecat.com/docs/api-v2#tag/Overview-(v2)/Should-I-use-this-REST-API-or-the-RevenueCat-SDK) so I created a ‘secret’ key with minimal read only permissions. See how I go. Man your doco sure is a maze, maybe it’s just me, I guess RC does a lot of different stuff… still.
hey
I believe you’ve already figured it out, but I’ll answer anyway in case it’s helpful for others.
does this mean in order to access my RC account from my javascript backend, I need to setup a RevenueCat Billing APP (With an associated Stripe account)??
No, that’s not necessary. You can use RevenueCat’s API from your backend without creating a RevenueCat Billing App. RevenueCat provides two APIs:
- API v1: Primarily used by our SDKs but also supports server-to-server interaction. Many endpoints can be accessed with an app’s public API key, while more sensitive actions (e.g., deleting a customer or granting a refund) require a secret key.
- API v2: Designed for server-to-server interactions and not used by our SDKs. All endpoints require a secret key.
Man your doco sure is a maze, maybe it’s just me, I guess RC does a lot of different stuff… still.
Sorry to hear that navigating our documentation felt tricky. RevenueCat does cover a lot of ground, so we’re always looking for ways to make things clearer. Was there anything specific that stood out as confusing? Your feedback would be really helpful!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.