Skip to main content
Question

Why is there no "app_id" sent with the webhook for PROMOTIONAL products?


Forum|alt.badge.img+7

Hi,

we are using webhooks for updating user profiles in our database. So far everything worked fine, but from today (or maybe yesterday) we can’t do this anymore for promotional “purchases” because the webhook event body is missing the app_id property. It is there for regular purchases.

promotional:

"api_version": "1.0",
  "event": {
    "aliases": [
      "xxxxxxxxxxxxxxxx",
      "$RCAnonymousID: xxxxxxxx"
    ],
    "app_user_id": "xxxxxxxxxxxxxxxx",

regular:

  "api_version": "1.0",
  "event": {
    "aliases": [
      "$RCAnonymousID:xxxxxxxxxxxxxxxxxxxxxxxx"
    ],
    "app_id": "appd5b6xxxxxxxx",
    "app_user_id": "$xxxxxxxxxxxxxxxxxxxxxxxx",

Is this intentional or a bug?

Thanks!

This post has been closed for comments

3 replies

kaitlin
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 401 replies
  • March 20, 2025

Hi ​@womo!

This is intentional! The app_id isn’t included in webhooks for promotional purchases because, as a RevenueCat specific feature, the purchase isn’t tied to a specific app within your project but rather the project as a whole. 


Forum|alt.badge.img+7
  • Author
  • Member
  • 5 replies
  • March 20, 2025

Hi. Thanks for the explanation. :)

so what is the correct approach for granting entitlements to users with the API? 
Sometimes we distribute the app on the web and need to activate an entitlement for an app. That means a project, not an specific app (android / ios etc). We have three projects on RC and need to identify the purchased app in the webhook. 
 


kaitlin
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 401 replies
  • March 27, 2025

Hey ​@womo,

Thanks for elaborating on your use case - unfortunately we don’t expose that information in promotional webhooks. 

What information do you have about the user when they download the app from the web?


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings