Hi everyone!
I maintain a small WordPress plugin that can pull your Trakt history into your site. I just realized that its import feature stopped working properly a few months back. It appears my implementation did not take into account some recent pagination changes.
The pagination page still says:
Methods with
Pagination will load 1 page of 10 items by default.
with a parameter table giving limit a default of 10. It was last updated in May 2025.
As far as I can tell there is no single default anymore. Sending no page or limit at all, and reading x-pagination-limit back:
| Endpoint | x-pagination-limit |
|---|---|
/users/{id}/history |
100 |
/movies/trending, /movies/popular, /movies/anticipated |
100 |
/shows/trending, /shows/popular |
100 |
/users/{id}/watchlist, /users/{id}/lists |
100 |
/search/{type} |
50 |
/movies/{id}/comments, /shows/{id}/comments |
10 |
So comments still match the documented 10, search is 50, and everything else I tried is 100.
There is also a maximum of 250 since June 15, and going past it is clamped rather than refused. limit=1000 on my history comes back with 250 items and x-pagination-limit: 250, which is an easy way to read a quarter of what you expected without anything looking wrong.
After searching for a bit, I found that the “100” change was announced. It was mentioned in discussion #681 on March 17, and rolled out April 15. No big surprise there, my plugin was old code leaning on a documented default it should have been sending explicitly anyway 
Of note, that discussion is scoped to lists, watchlist, favorites and collection, and discussion #775 covers the watched endpoints. Neither mentions /users/{id}/history, which was already paginated before any of this, so its default changed without being named anywhere I could find.
I have written both parts up on GitHub:
- issue #924 for the docs being out of date
- PR #925, a one-line change so the
limitparameter in the API reference mentions the 250 cap and warns off relying on the default
Someone hit the list version of this back in March and had to be pointed at the GitHub discussion to work out what had happened, so I do not think I am the only one.
Short version for anyone debugging something similar: send page and limit explicitly, and do not trust the limit you asked for either. If I have missed a page where this is written down already, let me know
Devs, if you’re stumbling across this thread, hopefully my small PR helps!
Thank you!