Skip to main content

APIKeyQuery

API key authentication using a query parameter. This defines the name of the query parameter that should be provided in the request with the API key and integrates that into the OpenAPI documentation. It extracts the key value sent in the query parameter automatically and provides it as the dependency result. But it doesn’t define how to send that API key to the client.

Parameters

str
required
Query parameter name.
str | None
default:"None"
Security scheme name. It will be included in the generated OpenAPI (e.g. visible at /docs).
str | None
default:"None"
Security scheme description. It will be included in the generated OpenAPI (e.g. visible at /docs).
bool
default:"True"
By default, if the query parameter is not provided, APIKeyQuery will automatically cancel the request and send the client an error.If auto_error is set to False, when the query parameter is not available, instead of erroring out, the dependency result will be None.This is useful when you want to have optional authentication or when you want to have authentication that can be provided in one of multiple optional ways (for example, in a query parameter or in an HTTP Bearer token).

Example


APIKeyHeader

API key authentication using a header. This defines the name of the header that should be provided in the request with the API key and integrates that into the OpenAPI documentation. It extracts the key value sent in the header automatically and provides it as the dependency result. But it doesn’t define how to send that key to the client.

Parameters

str
required
Header name.
str | None
default:"None"
Security scheme name. It will be included in the generated OpenAPI (e.g. visible at /docs).
str | None
default:"None"
Security scheme description. It will be included in the generated OpenAPI (e.g. visible at /docs).
bool
default:"True"
By default, if the header is not provided, APIKeyHeader will automatically cancel the request and send the client an error.If auto_error is set to False, when the header is not available, instead of erroring out, the dependency result will be None.This is useful when you want to have optional authentication or when you want to have authentication that can be provided in one of multiple optional ways (for example, in a header or in an HTTP Bearer token).

Example


APIKeyCookie

API key authentication using a cookie. This defines the name of the cookie that should be provided in the request with the API key and integrates that into the OpenAPI documentation. It extracts the key value sent in the cookie automatically and provides it as the dependency result. But it doesn’t define how to set that cookie.

Parameters

str
required
Cookie name.
str | None
default:"None"
Security scheme name. It will be included in the generated OpenAPI (e.g. visible at /docs).
str | None
default:"None"
Security scheme description. It will be included in the generated OpenAPI (e.g. visible at /docs).
bool
default:"True"
By default, if the cookie is not provided, APIKeyCookie will automatically cancel the request and send the client an error.If auto_error is set to False, when the cookie is not available, instead of erroring out, the dependency result will be None.This is useful when you want to have optional authentication or when you want to have authentication that can be provided in one of multiple optional ways (for example, in a cookie or in an HTTP Bearer token).

Example