Dear @Alan_19 and @MarcBaumbach I’ve came across the problem too. We at OptiMonk are a website personalization tool that offers subscription popups and embedded solutions and some of our customers are required to use double opt-in, but the Admin API’s Customer resource (we’re using the REST API) doesn’t triggers the DOI confirmation.
I think we tried the same as @MarcBaumbach earlier this year.
Is there and news @Alan_19 about the DOI triggering via Admin API?
Can you elaborate WHY the API does not work this way we need? Why on earth does the marketing opt-in level contain the confirmed_opt_in setting in a PUT action if it doesn’t work - both in REST and GraphQL the option is there?
Thanks in advance.