| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 162 |
| Technical Name |
bjet_api_log |
| License | LGPL-3 |
| Website | https://bjetpro.com/ |
| Versions | 17.0 18.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 162 |
| Technical Name |
bjet_api_log |
| License | LGPL-3 |
| Website | https://bjetpro.com/ |
| Versions | 17.0 18.0 |
Everything you need to track HTTP requests
A lightweight, developer-friendly tool to log, inspect, and audit every HTTP request and response your Odoo instance makes or receives.
Bidirectional Logging
Log inbound and outbound HTTP calls for full visibility, enhancing transparency and accountability.
Full Capture
Record all HTTP requests - URL, method, headers, params, bodies, status, timestamps.
Smart Naming
Generate descriptive log titles with timestamps for easy identification and quick analysis.
Multi-company ready
Organize logs by company for efficient management and easy search in a multi-company environment.
Community & Enterprise
Compatible with Community & Enterprise. Enjoy seamless performance and integration.
Compatible with Odoo 18.0
Optimized for seamless integration with Odoo 18.0. This tool is released under the LGPL-3 license.
What Gets Logged?
Direction (In / Out)
Response status code
Endpoint URL and HTTP method
Response body
Headers and query parameters
Timestamps and duration
Request body
Company context
Where to find it in Odoo
- Go to Technical -> BJET API -> LOGs.
- Open any entry to inspect request/response details.
- Use filters to narrow by date, method, URL, or status code.
Why teams use BJET API Log
Streamline development, improve performance, and maintain compliance
Enhanced debugging
Reproduce issues quickly with full request/response context, including headers.
Performance insights
Compare timestamps and status codes to spot slow endpoints and flaky integrations.
Audit & compliance
Keep a traceable history of API activity for security reviews and incident analysis.
Contact us
Need help, a fix, or an enhancement? Contact the BJET team.
Please log in to comment on this module