Will updating user_properties to "(none)" value with HTTP API V2 revert back to not provided?

Hi Amplitude community,

I wonder of this use case. Let’s say that I need to know if a user a subscriber and want to put it to user_properties. this is the case A user do::

1. Mon: user joined
2. Wed: user subscribed
3. Sat: user unsubsribed

if let’s say I user HTTP API V2 to update the user properties called `is_subscribe`

1. I don’t want the user to have any `is_subscribe` so not doing anything
2. update `is)subscribe` to a string: “yes”
3. (here is my question) -- I want to revert to the first state

So for 3, what value that I have to use for HTTP API V2 ya? I know that the value of non existed properties is (none). With that being said, if I update `is_subscribe` to a string “(none)”, will this be merged to Amplitude value of <non-existent> / <not provided>?

Thanks!