I’m trying to make the most recent subscription for a contact ACTIVE using the Rest v2 API.
I’m able to make the call and I’m using update_mask to only update two things: whether the subscription is active and whether auto-charge is on or off. It has no problem setting the auto-charge to on or off using “true” or “false” for the “auto_charge” param … but for the “active” param (which is also “true” or “false”) it will change it to either “active” or “inactive” both of which come up as INVALID in the drop-down because the actual option value is “Active” or “Inactive” (first letter is capitalized) in the drop-down (so there is no match).
Is there something else I should be doing to make it match correctly or is this a bug?
Thanks for reporting this. I tested it and was able to reproduce the issue. I’ll bring it up with the team and will keep you updated once it’s resolved.
Thank you! I tried to do the same thing via the XML-RPC API and that worked correctly, so I’ll use the XML-RPC for now until we can get the bug out of the REST v2 API.
1 Like
@geekgoddess, just a quick update. We’ve implemented a fix, and it’s currently available in our testing environment. I’ll keep you posted once it’s released.
1 Like
Thank you! For now, I’m using the XML-RPC (so I guess I have a year to update, haha). But seriously, I appreciate the devs there not letting this fall through the cracks. I hope we find (and fix) all of these issues before the end of next year. Will be looking for the release notification from you. 
1 Like