Hey @luismiguells! 

If I’m understanding you correctly, what you’d like to do is pull a list of every subscription (i.e. channel)  type and message type possible.

If that’s the case, you can try looking at the GET methods for Channels and Message Types, which will correspond to those which are defined in your project settings (Settings > Current Project > Message Channels & Types). Once you have those, you can tie together what each individual user’s subscriptions are via the IDs.

GET Channels API Docs

GET MessageTypes API Docs

I am not experienced with the /subscriptions endpoints you mentioned so if there are any special considerations to them, this guidance may not be helpful, but for most use cases this approach will get you what you’d otherwise be looking for from a /subscriptions GET request.

Hope that’s helpful! Let me know if you have any follow up questions.

Hey @drakeballew thanks for the answer. I can take a look in the approach you mentioned, and I’ll let you know. So far as I understand the subscriptions endpoints are more related to POST data in Iterable. So, I think your approach can work.

@luismiguells - no prob! And yes, my guess is that the /subscription endpoints are kind of just simplifying the means by which we’d manipulate the channels and message types are associated with the user object/user profile. So likely just POST/PATCH endpoints.

If things work out, I’d appreciate it if you’d mark my response as “best answer,” or let us know what you find out if they don’t. 

Have a great day!