| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 1532 |
| Technical Name |
bjet_api_sync |
| License | OPL-1 |
| Website | https://bjetpro.com/ |
| Versions | 17.0 18.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 1532 |
| Technical Name |
bjet_api_sync |
| License | OPL-1 |
| Website | https://bjetpro.com/ |
| Versions | 17.0 18.0 |
The BJet API Synchronization module makes it easy to integrate Odoo with any CRM, ERP, e-commerce, or marketing platform without spending resources on developing and maintaining dozens of custom solutions.
The BJet API Synchronization module makes it easy to integrate Odoo with any CRM, ERP, e-commerce, or marketing platform without spending resources on developing and maintaining dozens of custom solutions.
Instead of fragmented modules that are hard to maintain and need to be rewritten every time requirements change, you get a single universal configuration point with:
-
centralized logs and error control;
-
built-in timeout management and retries;
-
flexible triggers (automatic or manual);
-
the ability for two-way data exchange.
Versatility
Works with any API using common methods (CRUD, Auth, filters).
Scalability
Connect new systems or platforms without rewriting code.
Transparency
All integrations are monitored and controlled in one place.
Flexibility
Adjust via configs (mapping, filters) - no new coding needed.
Bidirectional Synchronization
-
Inbound Processing - Receive data from external systems into Odoo
-
Outbound Processing - Send Odoo data to external systems
Integration Modes
-
Real-Time Integration - Synchronize data immediately as changes occur
-
Scheduled Operations - Automated synchronization through cron jobs
Authentication Support
-
No Authentication - For public or internal APIs
-
Basic Authentication - Username and password access
-
Bearer Token - API key or token authentication
-
Custom Headers - Additional authentication headers
HTTP Protocol Support
-
Full REST Support - GET, POST, PUT, and DELETE methods
-
Custom Endpoints - Configurable API endpoint definitions
-
Parameter Handling - URL parameters and query strings
-
Header Management - Custom HTTP headers configuration
Data Transformation
-
Field Mapping - Visual alignment between Odoo fields and API keys
-
Python Scripting - Advanced data transformations
-
Value Calculation - Multiple methods for computing values
-
Relational Data - Support for Many2one, One2many, Many2many
Automation Integration
-
Cron Jobs - Schedule-based automatic synchronization
-
Server Actions - Manual triggers via Odoo interface
-
Base Automation - Event-driven synchronization
-
Trigger Configuration - Flexible synchronization rules
Monitoring and Debugging
-
Request Logging - Complete audit trail of API communications
-
Error Tracking - Detailed error messages with status codes
-
Performance Settings â Configurable timeouts
-
Debug Support - Comprehensive troubleshooting logs
Documentation
Find all the resources you need to set up, configure, and get the most out of BJet API Synchronization.
Contact us
Need help, a fix, or an enhancement? Contact the BJET team.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module