Hey @Publipresse My understanding of the problem you are trying to solve is expiration of members access to content when their subscription ends in the Aboweb.
Couple things to clarify upfront:
- Member API is in beta at the moment and will change, so you will have to keep an eye on any custom integration you make, so things don’t break.
- If you want to have paid member access control you’d need to connect Stripe to your instance. My understanding of this phrase: “Réglement CB avec TPE intégré (Stripe) et Sepa (Slimpay)” is that your platform already integrates with it.
There is no concept of
end_date on members records themselves. Ghost controls access to content through status of the subscription connected to the member -
members_stripe_customers_subscriptions.status. It is changed on the
current_period_end by Stripe triggering a webhook. Based on this logic you won’t need any “end_date” added to the member, rather you’d need to connect their
stripe_customer_id when importing though CSV and the rest should happen automatically.
Alternatively, if the platform you are using doesn’t have Stripe but the other provider they listed in the reference then there could be 2 options:
- Work with your platform and help them create a Zapier integration @DavidDarnes mentioned above.
- Write some kind of script running at intervals of time (e.g. CRON), that would remove members through the API once their membership expires on your platform.
Hope this gives enough context and you could work out the best solution