- Issue with /v1/updatesub
Re: Issue with /v1/updatesub
toggle quoted messageShow quoted text
It should now accept sub_id. If group_id is passed in as well, it will be ignored.
On Thu, Apr 25, 2019 at 8:56 AM Eric Searcy <eric@...
I'm calling updatesub as described in the documentation, and I'm getting an error.
curl -v -u $GROUPIO_TOKEN: -d sub_id=##### -d sub_notify=sub_notify_none
(Where ##### is the returned "id" field of the membership info object when I ran /v1/getsub against a group_id I'm subscribed to.)
I can work around the error by adding group_id to the request. Subscriptions seem to be globally unique identifiers, so the way the API documents it seems like it should work.
1) Can either the docs be updated, or the API be changed to match the docs?
2) If you change the API to match the docs, can you ensure that any passed group_id is just ignored (so it doesn't break backwards compatibility).
Join email@example.com to automatically receive all group messages.