Skip to main content

Hello Community,


I hope this message finds you well. I am currently in the process of submitting an app for the the marketplace with Monday monetization. I have been following the provided documentation here, but I have encountered a bit of confusion regarding the order of steps.


According to the documentation, the second step is to complete a form to become an approved Monday vendor. However, in this form, there is a field labeled “App Name” that requests information about an app that is either in review or already in the marketplace.


This seems to create a bit of a circular issue since, at this stage, I haven’t yet submitted my app for marketplace approval (Step 5), and thus, I don’t have an app already in the marketplace (or in review) to provide in this field.


Could you please provide clarification on the proper order of steps or how to proceed in this scenario? I want to ensure that I follow the correct process and provide all necessary information accurately.


Thank you for your assistance and guidance.


Best regards,

Hello @0xm3t1,

I agree that the process is a bit confusing. What you need to do is to first implement the monetization process in your app, by setting by a mock subscription.


Once you are certain that everything works correctly, you can submit your app for review. During the review process, you can go ahead and fill the form you mentioned in your question.

Hope this helps 🙂

Thank you so much for your helpful response! Your clarification makes perfect sense, and I appreciate you taking the time to explain the process.

Its just unfortunate there is no way to simulate the webhook events with that process. We can write our own simulation code, but we’re still guessing at the structures of the data since the example payloads don’t define specific types for each key that are possible, nor when they will be null or not. Plus how terribly the sequence of events, conditions for each event, etc. aren’t even documented. Its a crap shoot still.

Reply


Terms & ConditionsCookie settings