Scheduled Update: List IDs to become 64-bit integers


#1

In the coming months, Twitter will be expanding list IDs to 64-bit integers as previously mentioned in an earlier post. If you’re using our REST and Streaming APIs, you should confirm that your database, server-side and client-side code consume the safe string-based identifiers represented in “id_str” fields instead of the integer-based identifiers found in the “id” field of Twitter List objects and related references.

Previously we’ve migrated from 32-bit to 64-bit integer IDs for both user and tweet objects. As with those transitions, it is especially important to verify your application’s compatibility if you’re programming in Javascript. Issues while consuming 64-bit integers are easy to miss — the number will either overflow or underflow, representing an identifier for a completely different or non-existent object.

To ensure your application’s continued functionality, we strongly recommend modifying your applications to use our string-based IDs whenever present, regardless of the object type.