Skip to main content
Question

Get CustomerInfo on web after using mobile SDK

  • January 26, 2026
  • 4 replies
  • 34 views

Forum|alt.badge.img

Hi!

 

I am using an app that has 2 parts: a web part and a mobile part (for Android and iOS). Both are generated using the same codebase with Quasar, which in turn uses Capacitor to generate the mobile apps.

To allow users subscribe on the mobile part, I use the Capacitor SDK. I want users to be able to see their customer information (current plan, renewal dates...) in the app, be it the mobile or web version.

Obtaining this information on the mobile version is easy using the Capacitor SDK. However, I’m not sure about the recommended way to obtain this info on the web part.

 

My first idea was to use the Web SDK. However, there is no way to get a “web” API key, aside from setting up the RC Billing with Stripe, which I don’t intend to use. So I plan to use the Android key.

Here are my questions:

  • Is it OK to use public API key for Android store, as in theory the customer info is shared amongst every platform?
  • Is it the idiomatic way to use the web SDK as I plan to or is there some caveat that I missed?

 

Thanks !

4 replies

alejandra-wetsch
RevenueCat Staff
Forum|alt.badge.img+6

Hey ​@opack

Thank you for reaching out and providing details about your setup and what you’re trying to accomplish!

For your specific use case, I recommend using our REST API to fetch the user's subscription status on the Web. You can use the subscribers endpoint by passing the app_user_id and reading the entitlements object from the response. This endpoint returns the same data as getCustomerInfo in any mobile SDK.

Is it OK to use public API key for Android store, as in theory the customer info is shared amongst every platform?

As you mentioned, the customerInfo is shared amongst all platforms, so using it in your web application with an Android API Key may work. However, I recommend using the REST API described above instead to achieve optimal results.

Is it the idiomatic way to use the web SDK as I plan to or is there some caveat that I missed?

What you mentioned is correct. You could use the Web SDK, but as you mentioned, you will need to create a Web Billing app configuration. Another caveat is that, while you could use the Web SDK as ‘read-only’, additional libraries will be imported into your web app, such as ‘Stripe’, that you wouldn’t need.

I hope this helps!


Forum|alt.badge.img
  • Author
  • New Member
  • January 28, 2026

Thanks for the answer!

 

However, in the meantime, I have already implemented the web SDK and thought I had finished this project because, in the end, it works well 😁. So, I'm not thrilled about the idea of removing this part and replacing it with REST API management 😥

Unfortunately, I note that there are significantly fewer fields in the `entitlement` returned by the REST API than in `CustomerInfo`. In particular, the fields `isActive`, `willRenew`, `store`, and `periodType`, which I currently display, are missing.

 

Regarding the Android API key, you say "may work": I would like to confirm that it "will work," including for iOS customers. When I display this information, I have no way of knowing whether the user subscribed via Google Play Store or Apple App Store (this information is in `CustomerInfo`), so I plan to always use the same key (Google's, for example) to obtain `CustomerInfo`.

(Note: I don't yet have the iOS part yet to test and check for myself, hence my question.)

 

Thanks again!


Forum|alt.badge.img
  • Author
  • New Member
  • January 29, 2026

I can now confirm that it’s not possible to use a Google Play store public API key with the Web SDK. When I do this with a valid key with real products, I get this error:

PurchasesError(code: InvalidCredentialsError, message: Invalid API key. Use your Web Billing API key.)

So, it seems like the only option I have is the REST API, but as I mentioned it seems to be lacking many data… 😢


alejandra-wetsch
RevenueCat Staff
Forum|alt.badge.img+6

Hey ​@opack

Thank you for following up!

Regarding the REST API, if you would like to get all this information, there’s another Endpoint that can help. We have an API endpoint that returns all the user's subscriptions and their associated entitlements. You can check it out here

To provide additional details, the customer_id passed as the URL parameter is the same as the app_user_id. Also, this is version 2 of our REST API, so you may want to check the following documentation to ensure everything is in place on your end for you to work with it.

I hope this makes it easier!