Pydantic Plugins

Experimental feature

Plugins support is experimental and is subject to change in minor releases. Developing plugins is not recommended until the feature becomes stable.

Pydantic allows users to create plugins that can be used to extend the functionality of the library.

Plugins are installed via Python entry points. You can read more about entry points in the Entry points specification from the Python Packaging Authority.

In case you have a project called my-pydantic-plugin, you can create a plugin by adding the following to your pyproject.toml:

[project.entry-points.pydantic]
my_plugin = "my_pydantic_plugin:plugin"

The entry point group is pydantic, my_plugin is the name of the plugin, my_pydantic_plugin is the module to load plugin object from, and plugin is the object name to load.

Plugins are loaded in the order they are found, and the order they are found is not guaranteed.

As a user, you can modify the behavior of the plugin in a BaseModel using the plugin_settings Model Config argument or class keyword argument. This argument takes a dictionary of settings that will be passed to all plugins as is. The plugin can then use these settings to modify its behavior. It is recommended for plugins to separate their settings into their own dedicates keys in a plugin specific key in the plugin_settings dictionary.

from pydantic import BaseModel


class Foo(BaseModel, plugin_settings={'my-plugin': {'observe': 'all'}}):
    ...

Build a plugin

API Documentation

pydantic.plugin

Pydantic provides an API for creating plugins. The API is exposed via the pydantic.plugin module.

On your plugin you can wrap the following methods:

• validate_python: Used to validate the data from a Python object.
• validate_json: Used to validate the data from a JSON string.
• validate_strings: Used to validate the data from strings.

For each method, you can implement the following callbacks:

• on_enter: Called before the validation of a field starts.
• on_success: Called when the validation of a field succeeds.
• on_error: Called when the validation of a field fails.

Let's see an example of a plugin that wraps the validate_python method of the SchemaValidator.

from typing import Any, Dict, Optional, Union

from pydantic_core import CoreConfig, CoreSchema, ValidationError

from pydantic.plugin import (
    NewSchemaReturns,
    PydanticPluginProtocol,
    SchemaKind,
    SchemaTypePath,
    ValidatePythonHandlerProtocol,
)


class OnValidatePython(ValidatePythonHandlerProtocol):
    def on_enter(
        self,
        input: Any,
        *,
        strict: Optional[bool] = None,
        from_attributes: Optional[bool] = None,
        context: Optional[Dict[str, Any]] = None,
        self_instance: Optional[Any] = None,
    ) -> None:
        print(input)

    def on_success(self, result: Any) -> None:
        print(result)

    def on_error(self, error: ValidationError) -> None:
        print(error.json())


class Plugin(PydanticPluginProtocol):
    def new_schema_validator(
        self,
        schema: CoreSchema,
        schema_type: Any,
        schema_type_path: SchemaTypePath,
        schema_kind: SchemaKind,
        config: Union[CoreConfig, None],
        plugin_settings: Dict[str, object],
    ) -> NewSchemaReturns:
        return OnValidatePython(), None, None


plugin = Plugin()

Using Plugin Settings

Consider that you have a plugin called setting called "observer", then you can use it like this:

from pydantic import BaseModel


class Foo(BaseModel, plugin_settings={'observer': 'all'}):
    ...

On each validation call, the plugin_settings will be passed to a callable registered for the events.

Disabling Plugins

You can use environment variable PYDANTIC_DISABLE_PLUGINS to disable all or specific plugin(s).

Environment Variable	Allowed Values	Description
PYDANTIC_DISABLE_PLUGINS	__all__, 1, true	Disables all plugins
	Comma-separated string (e.g. my-plugin-1,my-plugin2)	Disables specified plugin(s)