python-authenticationlisted

# Authenticating an APIMatic Python SDK client How you authenticate depends on the security scheme(s) the API uses. APIMatic generates **one keyword argument per scheme** on the client (and on `Configuration`), and — for every scheme except custom authentication — **a credentials class to pass to it**, under `paypalserversdk/http/auth/`. You build the object and pass it in when constructing the client (see `python-client-initialization`). > **Custom authentication is the exception.** Its module holds only the handler class (e.g. > `class CustomAuth(HeaderAuth)`), constructed from the whole `Configuration` and shipped as a stub with > an empty `auth_params` and `# TODO` comments where the credential values belong. There is **no > `{Scheme}Credentials` class to build**, even though the `{scheme}_credentials` keyword argument still > exists on the client. Nothing here is configurable from your application: custom authentication means > *the SDK itself* has to be completed or regenerated. **A custom *header* or custom *query-parameter* > scheme is not this case** — those are ordinary API-key schemes with a credentials class and a > `doc/auth/` page. Check the scheme's module for a credentials class before writing the call. > **Every identifier in this skill is a placeholder — none of these snippets will import as written.** > Auth module names, class names, constructor arguments and client kwargs all differ between SDKs: one > has `api_key.py`/`ApiKeyCredentials`, another `api