GET /campaign should not automatically filter on active

Posted in General by Jamie Phelps Mon Mar 11 2019 18:09:52 GMT+0000 (Coordinated Universal Time)·3·Viewed 182 times

I was a little surprised today to figure out that unless I specifically ask for campaigns with `"active": false`, a `GET` request for `/campaign` will limit its results to active campaigns. This is inefficient as it means two API calls to get all the campaigns. We *have* a way to ask for only the active campaigns; please don't force this behavior when what the request is for is really all of the campaigns.
Mar 12, 2019

Hello, we have tested this and we are not finding this behavior and cannot reproduce. Possibly it is because the results are paginated and the first 50 campaigns are all active.

If you want to force the results to include both active and inactive you can add "active":[0,1] but this should not be necessary.

Mar 12, 2019

Ah, you're correct. I wasn't aware that it was paginating. Sorry for the bother. Is there a way from the API response to know that there is additional data to be paginated or does one simply have to make an additional API request with an offset to get an empty result set?

Mar 13, 2019

This is a request we've gotten before. Thanks for the feedback.

Markdown is allowed