On the other hand I assume without moving toquery_parameters we wouldn't really be able make good use of TypedDict here?

The TypedDict means a fixed keys. I believe it is impossible to have a TypedDict where only some keys have fixed keys and typed values.

the user code more pythonic.

Isn't it more explicit to have a dedicated keyword argument to add extra HTTP query instead of implicitly converting extra arguments.

That's true. My thinking was more that for the higher-level functions, most of the time the query parameters are the only arguments users need to care about, and it's the other arguments that are more like extra args. So it feels more natural (to me) to use them like that as arguments rather than nesting them in a dict. For some custom methods/endpoints for example, we even expose them directly.

But maybe we should think about having a dedicated object that we can validate a bit in the long run. I think@JohnVillalovos had some similar ideas in the past regarding this, though.

It should be possible to have common and documented HTTP query parameters to still have named keys in the TypedDict. For example,sudo query. The undocumented keys can fallback to thequery_parameters.