Skip to main content
Odoo Community Association

Endpoint route handler

Beta License: LGPL-3 OCA/web-api Translate me on Weblate Try me on Runboat

Technical module that provides a base handler for adding and removing controller routes on the fly.

Can be used as a mixin or as a tool.

Rules can also provide a generator to yield many routes computed from the code instead of a single handler (see Usage).

Table of contents

Usage

As a mixin

Use standard Odoo inheritance:

class MyModel(models.Model):
    _name = "my.model"
    _inherit = "endpoint.route.handler"

Once you have this, each my.model record will generate a route. You can have a look at the endpoint module to see a real life example.

The options of the routing rules are defined by the method _default_endpoint_options. Here’s an example from the endpoint module:

def _default_endpoint_options_handler(self):
    return {
        "klass_dotted_path": "odoo.addons.endpoint.controllers.main.EndpointController",
        "method_name": "auto_endpoint",
        "default_pargs": (self.route,),
    }

As you can see, you have to pass the references to the controller class and the method to use when the endpoint is called. And you can prepare some default arguments to pass. In this case, the route of the current record.

As a tool

Initialize non stored route handlers and generate routes from them. For instance:

route_handler = self.env["endpoint.route.handler.tool"]
endpoint_handler = MyController()._my_handler
vals = {
    "name": "My custom route",
    "route": "/my/custom/route",
    "request_method": "GET",
    "auth_type": "public",
}
new_route = route_handler.new(vals)
new_route._register_controller()

You can override options and define - for instance - a different controller method:

options = {
    "handler": {
        "klass_dotted_path": "odoo.addons.my_module.controllers.SpecialController",
        "method_name": "my_special_handler",
    }
}
new_route._register_controller(options=options)

Of course, what happens when the endpoint gets called depends on the logic defined on the controller method.

In both cases (mixin and tool) when a new route is generated or an existing one is updated, the ir.http.routing_map (which holds all Odoo controllers) will be updated.

You can see a real life example on shopfloor.app model.

Generated routes

A rule can provide a generator instead of a handler. The generator is called when the routing map is built and yields any number of (url, endpoint) pairs. This way, a single row in the endpoint_route table can serve many routes computed from the code (e.g. all the methods exposed by a set of services) and new routes do not require any update of the table.

The preferred way is to point to a model method, which can be extended via standard inheritance:

def _prepare_endpoint_rules(self, options=None):
    options = {
        "generator": {
            "model": self._name,
            "res_id": self.id,
            "method_name": "_generate_routes",
        }
    }
    return super()._prepare_endpoint_rules(options=options)

def _generate_routes(self, rule):
    for name in ("foo", "bar"):
        route = f"{rule.route}/{name}"
        endpoint = make_endpoint(
            MyController()._handle,
            {"routes": [route], "methods": ["POST"], "auth": "user"},
            pargs=(self.id, name),
        )
        yield route, endpoint

The method is called with superuser rights as the routing map can be built by any user. A python class can be used too, via klass_dotted_path, like for handlers.

Use utils.make_endpoint to build endpoints: it fills the routing keys that Odoo requires.

A generator must be fast, deterministic and must not write to the database. If it fails, the error is logged and its routes are skipped: the rest of the routing map is not affected.

The routes of the rule are refreshed when the rule changes (the routing map version is bumped) or when the code changes (as for any controller: restart the server).

Known issues / Roadmap

  • add api docs helpers

  • allow multiple HTTP methods on the same endpoint

  • multiple values for route and methods

    keep the same in the ui for now, later own we can imagine a multi-value selection or just add text field w/ proper validation and cleanup

    remove the route field in the table of endpoint_route

    support a comma separated list of routes maybe support comma separated list of methods use only routing.routes for generating the rule sort and freeze its values to update the endpoint hash

    catch dup route exception on the sync to detect duplicated routes and use the endpoint_hash to retrieve the real record (note: we could store more info in the routing information which will stay in the map)

    for customizing the rule behavior the endpoint the hook is to override the registry lookup

    make EndpointRule class overridable on the registry

NOTE in v16 we won’t care anymore about odoo controller so the lookup of the controller can be simplified to a basic py obj that holds the routing info.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Camptocamp

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

Current maintainer:

simahawk

This module is part of the OCA/web-api project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Metadata

Release files for odoo-addon-endpoint-route-handler 18.0.1.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for odoo-addon-endpoint-route-handler 18.0.1.2.0
File Interpreter ABI Platform
odoo_addon_endpoint_route_handler-18.0.1.2.0-py3-none-any.whl Python 3 none any Details

Release files / odoo_addon_endpoint_route_handler-18.0.1.2.0-py3-none-any.whl

Download URL odoo_addon_endpoint_route_handler-18.0.1.2.0-py3-none-any.whl
Size 60.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4836b6ec23b2515f0e3cb681ab2529d17ea42193d03d5026333667c1469dd4fb
BLAKE2b-256 checksum
How to use checksums
4dd10a807018fce1cea6d7caca5f80cc3715a800ee1bdeebb44ef11a0913ce33
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.4
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page