allow support for additional kwargs

Currently, the library fails if anything is provided in the request parameters that isn't hard-coded as function parameters. It would be good if additional/new API parameters can be called without the need to hard-code them every time.

This would touch:
#75
#74
#62
#66

Start by reviewing the request-parameter handling and the related issues #75, #74, #62, and #66. Determine how additional API parameters are currently rejected and define completion as allowing new parameters without hard-coding each one as a function parameter, with existing behavior preserved.

Written by the indexing model from the issue text.