Hey @tucosaurus - you’re correct, this isn’t something that can currently be checked via the API. I definitely get where you’re coming from though, happy to put a feature request through!
Just out of curiosity, how are you currently working around this? Are you using something like the below query?
Thanks @tucosaurus, appreciate you following up here. I just did some digging, and just want to clarify, are you using the segmentCreate mutation to pull that info by any chance?
On a “regular” customers object query, email_subscription_status isn’t a valid query argument, but it is one for the segmentCreate mutation. Just wanted to touch base to see if that’s what you’re using and if the issue is essentially that you can’t create the segment with the mutation using that query argument, since that should work.
Hey @tucosaurus - no worries! Thanks for clarifying, I’ll definitely put a feature request through for you on this. I can’t guarantee if/when the feature would be implemented, but will get one set up for you for sure so we can send this up to our product team.
Just out of curiosity. you’re just wanting something like this?
{
shop {
marketingDoubleOptinstatus
}
}
Wanted to make sure I’m getting your use case correct before I send this up - hope to speak soon!
Thanks for confirming @tucosaurus - I’ll get in touch with the team to see if I can share any info with you on this potentially being on our roadmap, but at the very least I’m more than happy to set up an official feature request for you on my end. Speak with you as soon as I have more info to share
Hey again @tucosaurus - just following up with this for you. I was able to get in touch with the customers/customer accounts product team on my end here and can confirm while we don’t have this on our product roadmap at the time, I’m going to log a feature request for double opt-in to be something API users can more easily access.
We do think it’s a good idea, and although I can’t guarantee if/when this will be enabled, I just wanted to let you know our developers are aware of your feature idea. Thanks for flagging this again!