Currently we accept only List for arguments that Telegram documents as "array". This limitation is rather unnecessary. Passing a tuple will in fact also work out of the box since the json module automatically converts tuples to json arrays.

IMO it's sane to expect every object that is iterable, with finite length and fixed order of elements to work - which brings us to Sequence. Once could argue that we don't strictly need fixed order and instead go for Collection, but for most objects, the order of elements does change the behavior of Telegram and using Sequence avoids one possible source of confusion for users. The only example I can think of where order doesn't matter are the (caption_)entities arguments …

This is also in symmetry with #3249, which accepts Sequence for class arguments and converts them to tuple.

The only downside of this approach is that we need one additional check somewhere in RequestParameter along the lines

if not isinstance(object, (tuple, list)):
    object = list(object)

as otherwise json.dumps would fail.

Edit: More precisely, the edit would be required here: