HomeApp StoreSecurity & Access ControlAdvanced API / Endpoint Access Control
Advanced API / Endpoint Access Control
Security & Access ControlAuraOdoo Verified

Advanced API / Endpoint Access Control

Block or rate-limit API routes per user/group.

Technical Specifications & Compatibility

Technical Module Name
Supported Odoo Versions
v19.0
License
Odoo
Deployment Support
Odoo OnlineOdoo.shOn Premise
Lines of Code
1052 lines (Python / XML / JS)

Overview & Description

Odoo 20.0 Community & Enterprise OPL-1 License Advanced API / Endpoint Access Control Block or rate-limit API routes by user, group, HTTP method, request type, and company with zero code modifications. Features server-side pre-dispatch enforcement, wildcard path matching, in-memory rate limiting, and searchable audit logs. Enterprise API Governance: Control access to JSON-RPC, HTTP controllers and JSON-2 endpoints with server-side pre-dispatch blocking and a cached rule set. Comprehensive API Security & Rate Limiting Engine Safeguard your Odoo system against API abuse, unauthorized controller access, and server overload without touching application source code. Endpoint & Method Control Block GET, POST, PUT, DELETE, and PATCH methods independently with wildcard URL path patterns. Dynamic Rate Limiting Set maximum request thresholds per user, IP address, or global window to stop automated scraping and flooding. Audit Logging & Caching Track every blocked or rate-limited request in searchable audit logs. The rule set is cached, so an allowed request only pays for a quick in-memory match. Module Overview Designed for system administrators, security officers, and enterprise integration teams. Standard Odoo lacks native endpoint-level access controls or route rate-limiting for external integrations, third-party mobile apps, and web controllers. Advanced API / Endpoint Access Control intercepts incoming HTTP requests directly inside ir.http._pre_dispatch before endpoint code executes. It allows administrators to define path rules, restrict HTTP methods, set rate limits by IP or user, log violations, and manage multi-company API permissions from an intuitive backend UI. Odoo Version 20.0 Hook Level ir.http._pre_dispatch Performance Cached Rule Set Audit Log Searchable Records Key Features Granular API routing, method restriction, and rate limiting capabilities. All HTTP Methods Controlled Granular method restriction per endpoint route: • Block GET, POST, PUT, DELETE, and PATCH • Restrict write/delete methods while allowing GET • Apply independent rules per HTTP verb • 403 Forbidden by default; 404 or 429 selectable per rule • No code modification required Request-Type Awareness Differentiate security enforcement by dispatcher type: • JSON-RPC API dispatcher rules • Standard HTTP controller route rules • JSON-2 API dispatcher rules • Custom API endpoint isolation • Precise dispatcher scope matching Wildcard Path Matching Flexible URL pattern matching engine: • Wildcard support: /api/* • Method call support: /web/dataset/call_kw/* • Exact path matching or prefix patterns • Case-sensitive, like Odoo routes; auth='none' routes are out of scope • Match multiple nested route paths Thread-Safe Rate Limiting Built-in rate limiter protecting server capacity: • Configurable max requests per time window • Scope per-user, per-IP, or globally • Thread-safe in-memory rate store • Returns 429 Too Many Requests status • Prevents denial-of-service and brute force Server-Side Pre-Dispatch Early-stage security check in request pipeline: • Intercepts requests in _pre_dispatch • Blocked calls never execute handler code • Protects database queries from unauthorized runs • Master on/off toggle in system settings • Allowed calls only pay for a cached in-memory match Audit Log & Caching Comprehensive compliance review & caching: • Optional audit recording for blocked calls • Stores client IP, timestamp, user, route, method and matched rule • Rule set cached with api.ormcache • Automatic cache invalidation on rule edit • Multi-company record rule isolation Business Benefits Essential security and governance for production Odoo environments. Prevent API Abuse & Server Overload Enforce rate limits per IP and per user to stop rogue scripts, web crawlers, and third-party integrations from consuming server resources or triggering high database loads. Enforce Least-Privilege API Security Restrict critical API endpoints (e.g. payment webhooks, customer datasets, export endpoints) to authorized users or groups without editing python controller files. Instant No-Code Policy Updates Add, update, or disable API access rules directly from the Odoo backend UI. Rule updates take effect immediately across all workers thanks to automatic cache invalidation. Complete Security Audit Visibility Maintain full audit trails of unauthorized API attempts. Search and filter blocked requests by IP address, user, route, or timestamp to quickly identify potential security threats. Screenshots & Interface Clean backend management interfaces for rules, settings, and audit logs. API Access Control Overview Overview banner demonstrating endpoint path rules, HTTP method selection, rate limiting thresholds, and audit log tracking. Rule Configuration View Endpoint Rule Form Define URL path patterns, select HTTP methods (GET, POST, etc.), set request type scopes, assign authorized groups/users, and configure rate limits. Supports wildcard matching like /api/v1/* to secure entire route hierarchies. Audit Log Dashboard Blocked Request Records Inspect blocked API calls with full details including IP address, user account, endpoint path, HTTP method, timestamp, and the rule that matched. Audit logging can be toggled on/off in General Settings to save database space. Workflow Simple 4-step administrative workflow for securing API endpoints. Step 1 Enable Security Activate Master API Control in Settings > API / Endpoint Access Control. Step 2 Create Endpoint Rule Enter route path (e.g. /api/*), select HTTP methods, and choose request type scope. Step 3 Set Limits & Users Assign authorized user groups and set rate limiting thresholds (e.g. 100 requests / 60 seconds). Step 4 Monitor Audit Logs Review blocked request attempts and rate limit triggers in the searchable Audit Log list. Configuration Flexible settings managed entirely from the Odoo backend. General Settings Enable Endpoint Security: Master switch to activate/deactivate pre-dispatch filtering. Enable Audit Logging: Toggle recording of blocked or rate-limited API calls. Default Response Code: 403 Forbidden unless the rule says 404 or 429. A blocked JSON-RPC call returns an Access Error that the web client shows as a normal dialog. Rule Setup Options Path Matching: Supports exact matches, wildcards (/api/*), or sub-path prefixes. HTTP Verbs: Checkboxes for GET, POST, PUT, DELETE, PATCH. Rate Limit Store: Thread-safe in-memory cache keyed per IP address or user ID. Technical Details High-performance architecture built into Odoo's HTTP dispatch lifecycle. Technical Name advanced_api_endpoint_control Odoo Version 20.0 License OPL-1 Dependencies base, web Enforcement Point ir.http._pre_dispatch override (Server-side pre-dispatch check) Caching Engine api.ormcache on the active rule set, cleared on every rule change Multi-Company Full multi-company support with owner_company_id and ir.access company domains Rate Limiting Thread-safe in-memory window store with auto-expiry cleanup Compatibility Fully compatible across Odoo versions and API frameworks. Odoo 20 Built for the Odoo 20.0 HTTP, JSON-RPC and JSON-2 dispatchers. All API Types Supports JSON-RPC, HTTP controllers and JSON-2 endpoints. High Concurrency Cached rule set; rate-limit counters are kept per worker, so the effective limit is multiplied by the worker count. Supported Editions Seamless execution across Community and Enterprise. Odoo Community Edition 100% compatible with Odoo Community Edition using standard base dependencies. Supported Odoo Enterprise Edition Fully compatible with Odoo Enterprise Edition, Odoo.sh, and cloud hosting environments. Supported Installation Guide Standard Odoo module installation steps. Extract Module Folder Extract the advanced_api_endpoint_control folder into your custom Odoo addons directory. Update Apps List Activate Developer Mode in Odoo Settings, navigate to Apps, and click Update Apps List. Install Module Search for advanced_api_endpoint_control or Advanced API / Endpoint Access Control in Apps and click Install. Configure Master Toggle Navigate to Settings > API / Endpoint Access Control and turn on the master toggle. Frequently Asked Questions Answers to common technical and operational questions. Very little. The active rule set is cached with Odoo's ormcache and dropped only when a rule is created, edited or deleted, so an allowed request costs one in-memory match per applicable rule. Yes. The rule path matching engine supports wildcard patterns such as `/api/*` or `/web/dataset/call_kw/*` to protect entire route trees with a single rule definition. Blocked requests are intercepted during `ir.http._pre_dispatch` before reaching the target endpoint controller code. The server immediately answers with HTTP 403 Forbidden, 404 or 429 Too Many Requests, as set on the rule. JSON-RPC callers get an Access Error instead of a bare 403, so the web client shows a regular error dialog rather than a "session expired" message. Yes. Rules include `owner_company_id` and `company_ids` fields supported by standard `ir.rule` security filters, allowing distinct API policies per company branch. Changelog Release history and updates. Version 20.0.1.0.0 Odoo 20 migration Ported to Odoo 20: ir.access.csv company domains replace the old ACL and record-rule pair. Request-type filter now stores the real dispatcher type (HTTP, JSON-RPC, JSON-2). Rules saved as "JSON" or "Legacy JSON" never matched a request before; they are converted to JSON-RPC on upgrade. Audit entries are written on their own cursor, so they are kept when the request is rejected (they used to be rolled back with it). A failing audit write can no longer turn a block into a server error. Blocked JSON-RPC calls return an Access Error, so the web client no longer reports a "session expired". The settings defaults are no longer reset by a module upgrade. The dry-run endpoint honours the master switch; rules sharing a path pattern are merged in the session data. AAEC administrators cannot lock themselves out of the rule screens; the superuser is exempt. Added a Python test-suite and JavaScript unit tests. Version 1.0 Initial Release Initial production release of Advanced API / Endpoint Access Control. Implemented server-side pre-dispatch route filtering in `ir.http._pre_dispatch`. Added HTTP method restriction (GET, POST, PUT, DELETE, PATCH). Added request-type scope matching (JSON-RPC, HTTP, Legacy JSON). Built thread-safe in-memory rate limiting engine with configurable time windows. Integrated searchable Audit Log and ORMCache performance optimization. Need Support or Customization? Our team of Odoo security experts is available to assist you with installation, configuration, or custom API security rules. Aura Odoo Tech Professional Odoo Development & Security Services Visit Our Website © 2021-2026 Aura Odoo Tech. All Rights Reserved. Advanced API / Endpoint Access Control — Released under OPL-1 License.

Key Capabilities & Features

  • Block GET, POST, PUT, DELETE, and PATCH
  • Restrict write/delete methods while allowing GET
  • Apply independent rules per HTTP verb
  • 403 Forbidden by default; 404 or 429 selectable per rule
  • No code modification required
  • JSON-RPC API dispatcher rules
  • Standard HTTP controller route rules
  • JSON-2 API dispatcher rules
  • Custom API endpoint isolation
  • Precise dispatcher scope matching
  • Wildcard support: /api/*
  • Method call support: /web/dataset/call_kw/*
  • Exact path matching or prefix patterns
  • Case-sensitive, like Odoo routes; auth='none' routes are out of scope
  • Match multiple nested route paths
  • Configurable max requests per time window
  • Scope per-user, per-IP, or globally
  • Thread-safe in-memory rate store
  • Returns 429 Too Many Requests status
  • Prevents denial-of-service and brute force
  • Intercepts requests in _pre_dispatch
  • Blocked calls never execute handler code
  • Protects database queries from unauthorized runs
  • Master on/off toggle in system settings
  • Allowed calls only pay for a cached in-memory match
  • Optional audit recording for blocked calls
  • Stores client IP, timestamp, user, route, method and matched rule
  • Rule set cached with api.ormcache
  • Automatic cache invalidation on rule edit
  • Multi-company record rule isolation
  • Enable Endpoint Security: Master switch to activate/deactivate pre-dispatch filtering.
  • Enable Audit Logging: Toggle recording of blocked or rate-limited API calls.
  • Default Response Code: 403 Forbidden unless the rule says 404 or 429. A blocked JSON-RPC call returns an Access Error that the web client shows as a normal dialog.
  • Path Matching: Supports exact matches, wildcards (/api/*), or sub-path prefixes.
  • HTTP Verbs: Checkboxes for GET, POST, PUT, DELETE, PATCH.
  • Rate Limit Store: Thread-safe in-memory cache keyed per IP address or user ID.
  • Extract Module Folder Extract the advanced_api_endpoint_control folder into your custom Odoo addons directory.
  • Update Apps List Activate Developer Mode in Odoo Settings, navigate to Apps, and click Update Apps List.
  • Install Module Search for advanced_api_endpoint_control or Advanced API / Endpoint Access Control in Apps and click Install.
  • Configure Master Toggle Navigate to Settings > API / Endpoint Access Control and turn on the master toggle.
  • Ported to Odoo 20: ir.access.csv company domains replace the old ACL and record-rule pair.
  • Request-type filter now stores the real dispatcher type (HTTP, JSON-RPC, JSON-2). Rules saved as "JSON" or "Legacy JSON" never matched a request before; they are converted to JSON-RPC on upgrade.
  • Audit entries are written on their own cursor, so they are kept when the request is rejected (they used to be rolled back with it).
  • A failing audit write can no longer turn a block into a server error.
  • Blocked JSON-RPC calls return an Access Error, so the web client no longer reports a "session expired".
  • The settings defaults are no longer reset by a module upgrade.
  • The dry-run endpoint honours the master switch; rules sharing a path pattern are merged in the session data.
  • AAEC administrators cannot lock themselves out of the rule screens; the superuser is exempt.
  • Added a Python test-suite and JavaScript unit tests.
  • Initial production release of Advanced API / Endpoint Access Control.
  • Implemented server-side pre-dispatch route filtering in `ir.http._pre_dispatch`.
  • Added HTTP method restriction (GET, POST, PUT, DELETE, PATCH).
  • Added request-type scope matching (JSON-RPC, HTTP, Legacy JSON).
  • Built thread-safe in-memory rate limiting engine with configurable time windows.
  • Integrated searchable Audit Log and ORMCache performance optimization.
  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.

Screenshots & Previews

2 images available
Advanced API / Endpoint Access Control screenshot 1
Expand Preview
Advanced API / Endpoint Access Control screenshot 2
Expand Preview
The AuraOdoo Quality Guarantee
100% Tested

Verified with Odoo 17, 18, and 19 test pipelines for stability and no conflicts.

Clean Architecture

Built according to official Odoo guidelines and PEP 8 standards with zero bloat.

Dedicated Support

Free installation assistance and quick bug turnaround from our team.