Question

When requesting all adgroups or creatives for an account:

GET / adgroups?ids=act_accountid&access_token=...

the return includes a paging field, such as:

{
    *id*: {
        "data": [
            {
                ...
            },
            ...
        ],
    "count": 1500,
    "limit": 500,
    "offset": 0,
    "include_deleted": null
    "paging": {
             "next": ...
        },
    }
}

However, when requesting all adgroups for a campaign:

GET / adgroups?ids=campaign_id&limit=10&access_token=...

the return does not include a paging field:

{
    *id*: {
        "data": [
            {
                ...
            },
            ...
        ],
    "count": 15,
    "limit": 10,
    "offset": 0,
    "include_deleted": null
    }
}

Is this a bug, the intended operation, a future feature, etc? While I don’t have real examples of needing the paging field (currently none of our campaigns would exceed the default limit), I don’t want to design code that relies on a potentially non-existent paging field.

Thanks in advance.

Answer 1

Are you looking at the data object of the returned result set? If so, the paging object is not a child of data, rather it is a sibling. Try running your query thru the graph API Explorer and see if at the bottom of the results you can see the paging object.