Fetch subscribed channel ids

[ryanrampage1]

trafficstars

Looking for a way to get the channel ids that a user is subscribed to. I saw you can unsubscribe by sending the list up.

Because the setting is a user setting not a per device one, it would be great to see what the user is subscribed to on new devices, or if local data gets cleared out.

[ryanrampage1]

Bump here

[kdybicz]

I really hope that you @ryanrampage1 will have more luck than me #453 😅

[Ayyanchira]

Thank you for this feature request @ryanrampage1 and @kdybicz

Acknowledging that it as an important feature request and appreciate it :) . We will definitely consider it for inclusion in our roadmap later this year.

[amit3vedi]

@Ayyanchira Any update on this? and if this is not supported in android SDK is there any Rest API available to retrieve user's subscription list?

[Edjees]

@Ayyanchira i'm also curious if there's an update on this. I don't understand why /api/users/updateSubscriptions overwrites fields instead of merging them if there's no API for fetching the current user subscriptions. Without being able to grab the current user subscriptions, it's impossible to subscribe a user to a certain messageType without also unsubscribing him from all the other messageTypes.

[Edjees]

ah nevermind, there is Rest API for getting the subscriptions for a user: /api/users/byUserId https://api.iterable.com/api/docs#users_getUserById_0. (the email one works too) @amit3vedi I think this ^ should be the answer to your question: "is there any Rest API available to retrieve user's subscription list"

@Ayyanchira I think the docs should be updated to provide more clarity....I don't see anywhere that says that getting a user will also return the subscriptions. It might be worth it to have a dedicated Rest API for just grabbing user subscriptions without also grabbing all their datafields.

[ryanrampage1]

My opinion on this one year later is this is still core functionality that should be in the mobile SDK. This is an open source repo but it is an expensive tool. I would open a pr for it but I can't justify the cost of my time to add what should be expected functionality of an SDK or a product we pay for. Also not worth the tech debt to add in an Iterable only rest client next to the SDK.

Because the functionality is in a rest API already it should take the dev team a day at most to add. Really disappointing that they don't just get it done especially with the number of people requesting it here.