Using API to get a complete list of unsubscribers

[Richard Lund]

Hi.
I recently took over some existing code that interfaces with your API,
and after going through it and through the API documentation, I have
not found an answer yet, so I hope someone here can help me.

On your main site, I can export a complete list of all people who ever
clicked the unsubscribe link in our blasts.

Now I am trying to do the same through the API, and I can see a few
possible approaches - go through every single blast and receive a list
of unsubscribers for that blast (which would take forever given the
amount of blasts we send out) or use the filter system to only show me
email addresses of users who are marked as unsubscribed.
However, I cannot find the right information on how to do any of this.
It looks like the filter system cannot actually used to browse data
through the API.

So, am I stuck with storing all successful blast ids and then looping
through all of them and using that to get to the unsubscriber lists,
or is there any other way to do this?

Thanks in advance!

[Richard Lund]

Anyone?

Thanks!

[bhayes]

Hi Richard,

I think you can get this information in two ways. Either by looping
through all pages of people ( GET /audiences/{audience_id}/people.xml?
page=1&per_page=1000 ) or by looping through all blasts and requesting
every page of unsubscribes for each given blast.

I've had to aggregate blast specific data over a large number of
blasts through the API before. To my knowledge. In the particular case
I worked on, it was aggregating the reporting data across many blasts.
Based on the parameters for my particular case, the largest thing my
script had to deal with was 17,555 API requests in a single run that
took 1 hour, 25 minutes to complete. (about 3.4 request per second) A
significant portion of the time between requests was probably due to
the processing of each response before moving to the next request. So
the API has been pretty responsive during my use.

While the structure of the API doesn't make these types of things as
easy as it could be, in my experience it's worked well enough to get
the job done.

Hope that answers your question.

-Brandon

On Apr 27, 8:22 am, Richard Lund <rich...@myglobaldata.com> wrote:
> Anyone?
>
> Thanks!

[Richard Lund]

Hi, Brandon.

Thanks for your answer.

I was afraid it was going to be something along these lines, but I
guess what we are doing with Streamsend is a little unconventional,
and we have considerably less addresses per blast but in return we
have over 100 blasts per day, so that'll be a joy to implement :-/

In any case, thanks for clearing this up and providing me with the
information I needed to do that!

cu,
Richard