Introduce a consistent pagination and time-based filtering mechanism across list-based API endpoints (e.g. attacks, logs, item market, forum posts, faction members), such as limit, offset, since_timestamp, and until_timestamp.Many community tools and web applications need to sync data incrementally. Currently large danatasets must be repeatedly fetched, increasing API usage and backend load and forcing developers to implement client-side workarounds. From a backend/API development perspective (e.g. Django/RESTstyle APIs), server-side pagination and time-based filtering would improve performance, reliability, and scalability for both API consumers and Torn’s backend, without exposing any new gameplay advantages.
Example:
{
"attacks": [
{
"attack_id": 123456,
"attacker_id": 111,
"defender_id": 222,
"timestamp": 1704800000,
"result": "hospitalized"
}
],
"pagination": {
"limit": 100,
"offset": 0,
"total": 12453
}
}
Example request:/user/?selections=attacks&since=1704700000