Hey @OmarAlmonte
The /subscriptions/{$id} PATCH endpoint to update an existing subscription also requires a contact_id.
That makes sense for the POST /subscriptions/ endpoint which is CREATING a new subscription, but it doesn’t make sense when using PATCH to update an existing subscription. An existing subscription is already assigned to a contact_id.
This smells a bit like someone copy/pasted the code between endpoints and forgot to remove the unnecessary property.
To be fair it IS marked as “required” in the online docs, but it also says “Id of the contact to create the subscription for”, which is what makes me suspect a copy/paste bug.
contact_id wasn’t required to do a dsupdate through XML-RPC. and REST v1 seems to be missing the functionality altogether.
Supplying a different contact_id reassigns the subscription to a different contact. I don’t know if that was intentional.