Additional information on "older_than_token" for item based endpoints

[Peter200lx]

Additional information on "older_than_token" for item based endpoints

[Peter200lx]

First brush it looks like token for /api/fancollection/1/wishlist_items follows the pattern of /collection_items. However the 5 fields are:

1. Unix epoch timestamp of when fan "added" this item
2. "tralbum_id" of the item in question
3. "trablum_type" of the item in question
4. ?Unused?
5. ?Unused?

In this case it appears that the first three fields are all important for getting consistent responses.

From <div id="pagedata" data-blob="{JSON HERE}"> on your fan page look for .wishlist_data.last_token.

[nmwodarz]

Specifically related to api/fancollection/1/collection_items:

1. The timestamp and id are not necessary and can be left blank ::...
2. The tralbum_type is required to not be empty, but any value is fine ::foo:...
3. The index value is the only important part for this handler
   3.1. Any index value that is not a positive whole number is ignored and treated as an empty value, aka start at the first value you can give. (::foo:: or ::foo:bar: says start with the first item, ::foo:50: says start with the 51st item)
   3.2. This unfortunately means you can't get the extended information about the initial 45 items set on the users fan page (apart from something like automating swapping the first and section 45 item chunks)

Using this as a starting point, I was able to get an entire collection (matching the listed collection size) by setting older_than_token to f"{int(time.time())}::a::" (in Python).