Looking into the REST API v1 and v2 and what the web sdk does, I’ve noticed that https://api.revenuecat.com/rcbilling/v1/subscribers/<user_id>/products?id=<product_id> is kind of what we need. Is it safe to use? I don’t see any documentation around.
Thanks!
+6Hi
Thanks for reaching out. I’m happy to help.
That https://api.revenuecat.com/rcbilling/... path is not part of our publicly documented / supported REST APIs, and it’s primarily an internal endpoint used by Web Billing / the Web SDK. Because it’s undocumented, we can’t guarantee its stability (it may change without notice), so we don’t recommend integrating against it directly.
I’d recommend you to do the following instead:
To fetch a customer’s current subscription + entitlements state: use the v1 GET /subscribers/{app_user_id} endpoint. Docs here: https://www.revenuecat.com/docs/api-v1#tag/customers/operation/subscribers
If you’re syncing state from webhooks: we recommend calling GET /subscribers after receiving a webhook, so your backend always works with a consistent, canonical customer payload.
If what you actually want is the “web purchase flow” on the client: use the RevenueCat Web SDK (it’s designed for this and uses a Public API Key that’s safe to ship in production).
Hope this helps, let me know if you have any other questions.
Best,
Hussain
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
