Kindly help with more information about subscription data for integration apps

monday Apps & Developers
,
1

I have an integration app currently going through the review process and I needed some additional information about monetization.

1) For seat based plans, if one plan id offers a free plan (e.g. 0-3 seats) does that qualify as the compulsory free plan? Or is it necessary to apply for 14 days free trial category? I wasn’t sure about this after reading the pricing documentation.

2) I am currently querying the app subscription status using the following query. Now, if I choose 14 days free trial, does this query correctly return if the user is in the ‘14 days free trial’ period? Does this query correctly calculate the trial period and return false upon trial expiry while the app is in marketplace?

Adding to that, what would be the plain_id if the user is in trial period? (seat based pricing + integration app + 14 days free trial)?

query{ app_subscription { plan_id is_trial } }

3) While the user is on trial period, considering I have implemented the ‘14 days free trail’ for my integration app. Is the following query a valid strategy to get the seats count?

query {
apps_monetization_info {
seats_count
}
}

Thanks in advance for any help.

2

  1. Yes that covers the free plan, no trial is required.

  2. The subscription is actually included in the JWT payload at the “subscription” key once the app is monetized.

However, prior to monetization you can use the mock subscription capability in testing

The days_left for a trial represents how long until the trial expires. Renewal_date is the end of the trial. Is trial will change to false at the end of the 14 day trial.

For free plans the renewal date is 10 years in the future, with the days_left being that many days.

For free and trial plans - the billing_period is null.

  1. yes that would get the seats for purposes of knowing the account size. Trials would typically be your unlimited seat plan so you don’t block large accounts from the trial.
1 Like
3

Thanks Cody! That was really helpful.