Are there plans to add support to query things like app trials?

monday Apps & Developers Feature Requests - API and Apps Framework
1

Adding graphQL support for marketplace vendors would allow us to build out our own sales and reporting dashboards based on live data so that we can see whats happening with our shared customers now.

For example, I had a query where I forgot that I’d given a 200 user non-profit account a large discount. Being able to look this up would be very useful.

Some examples

  • query sales & discounts
  • query trials and when they expire

Someone who builds such a reporting facility for vendors may even put it on the marketplace for other vendors :wink:

Cc: @Matias.Monday @dipro

1 Like
2

Hi @dvdsmpsn
It’s a pleasure to e-meet you. I am Tom and I will introduce myself very soon to you.

In regards to your feedback. Thank you for making it so clear with an example that makes sense. Our team considers different solutions for developers, specifically when it comes to app business/sales info. However, I cannot provide a clear answer to your specific request at this point of time. I will inform you soon when there will be updates addressing this kind of capability.

1 Like
3

Hey @dvdsmpsn,

Just FYI, I changed the “category” of your post from Marketplace Builders’ only to Feature Requests so it gets in the request queue. This also allows other devs to “vote” on your request! :smiley:

2 Likes
4

:+1:Thumbs up from the CarbonWeb team! This would be super beneficial.

2 Likes
6

Quick update: we added a related field to our API – App installs

You can now see who installed your app and create your own reports. It’s a first step for an API for marketplace devs :slight_smile:

Check it out - App installs

2 Likes
7

Fantastic, @dipro !
Please, please, please prioritize the monetization APIs to allow us to see who subscribed, what plan, etc. This is crucial for us to better manage our subscriber base.
It’s important we can run such APIs not only on specific accounts, but also across all paying accounts for our app.
Happy to jump on a call to discuss further…

2 Likes
8

@dipro This is a great start, but I absolutely agree with @samicaracand – being able to see details such as the account_slug, user emails and all the fields that are available in the lifecycle webhooks (install/uninstall/app_subscription_* etc), and the amount charged would be a massive help.

1 Like
9

I’m actually still in disbelief that monday would call the monetization platform ready for production when it contained zero way to even look up your sales. But here we are nearly two years later.

1 Like
10

Hey friends, you can now get a list of app subscriptions for your app!

Check out the App Subscriptions object to learn more.

@dvdsmpsn your original request asked for both active subscriptions and trials. Since this request isn’t completely resolved yet, I’m going to rename it and keep it open.

3 Likes
11

@dipro this is very nice. thank you.

I’ve just tried the following:

query {
  app_subscriptions (
    app_id: 123456789   
  )  {
    cursor
    total_count 
    subscriptions {
      account_id
      period_type
      plan_id  
      monthly_price
      currency
      status
      renewal_date
      days_left
      discounts {
        value
        discount_type
      }
    }
  }
}

Are there plans for any of the following?

  • query by an array of app_ids, rather than just one? e.g. app_ids: [ID!]!
    • if we can start thinking about all apps a vendor may have rather than one app at a time
    • even just assume that this app_subscription object returns all the apps for a vendor, then have the ability to filter on app_ids if so required
  • add app_id , app_name and account_slug into the subscriptions object
  • add querying by period_type (monthly or yearly) so we can quickly see which yearly licenses are up for renewal soon
  • query by account_slug and account_id to target the latest info for a particular account
    • this could return multiple apps that a vendor has sold to the same client
  • add details of the account, rather than just the account_id only

Each of these would be massively useful for a more complete solution.

Again, many thanks.

4 Likes
12

Yes! Have to second David on these requests. The fuller the data set, the more useful on our side. Thank you @dipro !