I’ve noticed that the appSubscription object is missing confirmationUrl.
if a merchant declines the app charge then comes back after a few days (after the original confirmationUrl from the appSubscriptionCreate mutation has expired, how do we generate a new one?) the recurring_application_charges admin API returns the confirmationUrl with each pending app charge.
You can simply call the create subscription mutation again to create another new fresh confirmation URL.
Unfortunately, the confirmation URLs will expire, but the subscriptions that are never accepted aren’t deleted. So there is some noise on the events.
yes I was hoping to avoid that, surely if the admin API can return the confirmation URL then the graphql one can too?
The GraphQL mutation does return the confirmation URL, but only as a return to that mutation.
yes, but when i do that, it creates another appSubscription object, then you end up with a long list of cancelled ones which is not necessary. currently when using the Rest API, we don’t need to create a new recurring application charge as listing the existing ones will give us the confirmation URL for the existing app charge, so what i’m suggesting is if this can be done for the Rest API, it should be do-able and available for the graphQL API too, otherwise Shopify is just making it their own data more messy and complex.