Skip to main content
Question

Paywall JSON and Spec?

  • May 2, 2026
  • 2 replies
  • 32 views

Forum|alt.badge.img

I’m looking at making an implementation for .NET MAUI to support rendering Paywalls at the MAUI layer instead of trying to wrap the native Android/iOS SDKs to do it (the dependency graph is a bit of a nightmare to sort out for it unfortunately - the core SDKs aren’t too bad and I have working nicely).

Is there a spec or schema somewhere that I can get the details for the data returned when requesting paywalls?

I see the v2 api has an openapi spec which defines some parts, but there’s stuff like additionalProperties which seems like it could be platform specific.

Could you post specs for android/iOS at the very least, to understand more what the api might return? Alternatively, if you actually have a true unified version of the object model for web or flutter or some other framework, a comprehensive and complete spec for that would also be helpful.

Thanks

2 replies

guilherme
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • May 6, 2026

Hey ​@redth!

At the moment there isn't a published JSON Schema for the Paywalls V2 component model that I can point you at directly. The closest to a "unified" reference is the open-source hybrid SDKs, since they all decode the same JSON payload from our backend:

For the broader MAUI side, the closest thing the community has is Kebechet/Maui.RevenueCat.InAppBilling (also discussed here on our community forum), in case you haven’t come across it yet.

It's not officially supported by RevenueCat, but it's the only MAUI integration in the ecosystem and covers purchases, offerings, customer info and entitlements pretty well. Worth flagging it doesn't currently expose paywalls, so it won't help for the rendering piece you're tackling, but it could save you time on the rest, and the maintainer / issue tracker there is probably the best place to land any MAUI-specific questions or contributions.

Hope that helps!


Forum|alt.badge.img
  • Author
  • New Member
  • May 9, 2026

Thanks,

I’ve actually built my own .NET MAUI integration which works a bit differently than the existing ones out there: https://github.com/Redth/Plugin.RevenueCat

Full disclosure: I’m the engineering lead for the .NET MAUI SDK Team, so I am a bit biased of course.  I use RevenueCat in my own side project app and love it, but am always a bit sad that you all don’t have official support for .NET MAUI developers :(

My integration uses a native abstraction layer that is easier to bind against from the .NET side of things (since I control that API), and basically shuttles JSON across the wire from that layer whenever possible.  This makes it much easier to coordinate SDK updates when RevenueCat releases new versions (which I need to look at updating again now too), and makes for a nice cross platform API on all MAUI target platforms.

 

As for the paywall API’s, I did end up sending AI on a spelunking mission through those code repos and collecting samples, implementations, etc. to come up with a decent reference in addition to the v1 api endpoints.  It would still be great if you all considered publishing something a bit more formal for these types of scenarios.

I have a PR I’m working on to add Paywall support: https://github.com/Redth/Plugin.RevenueCat/pull/24 which is quite promising.

 

One thing that would be super helpful is if the previewer on the revenuecat paywall editor could give a link to, or allow a direct download of the json for the current state of the paywall being worked on.  This would help validate end to end that I’ve got things implemented properly, and would be nice for others using the library to be able to quickly validate their changes too with my sample app.