EDI WebService Core
Attach a webservice.backend to an EDI backend, and send EDI exchange files through it.
This module provides:
The webservice_backend_id field on edi.backend.
edi.webservice.send, a plain send_model_id handler that sends the exchange file through the backend’s webservice - no component dependency.
edi_webservice_component_oca provides the component-based equivalent (components/send.py) - a legacy integration style, kept in its own module so installing it (and component with it) is opt-in. edi_webservice_oca is now just a deprecated umbrella depending on both, kept to preserve existing installations.
Table of contents
Configuration
Go to “EDI -> Config -> Backends” and edit or create one. Find the tab “Webservice” and add a webservice. On the webservice record you can specify all the general parameters to connect to the service (see webservice_core README for more details).
On the exchange type you want to send through a webservice, go to the “Execution handlers” tab and set “Sender” to “EDI WebService Send Handler”.
By default the call uses the backend’s own configuration (URL, auth, …). If you want to take full control on if/how the webservice is used you can do it via the exchange type’s advanced settings.
Hence, assuming your webservice has a URL configured as `https://my.endpoint/%7Bpath%7D`:
execution_model:
send:
webservice:
method: post # mandatory
kwargs:
url_params:
path: endpoint1/foo
For each call related to this type, you’ll get a POST request against https://my.endpoint/endpoint/foo.
url_params can contain all the keys needed for URL interpolation.
In addition, you can use url to override the full url used for the call per exchange type.
If you want to send data as bytes you can use the option send_as_bytes like:
[...]
webservice:
send_as_bytes: true
[...]
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
Contributors
Simone Orsi <simone.orsi@camptocamp.com>
Enric Tobella <etobella@creublanca.es>
Maintainers
This module is maintained by the OCA.
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 maintainers:
This module is part of the OCA/edi-framework 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-edi-webservice-core-oca 18.0.1.1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| odoo_addon_edi_webservice_core_oca-18.0.1.1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_edi_webservice_core_oca-18.0.1.1.0.3-py3-none-any.whl
| Download URL | odoo_addon_edi_webservice_core_oca-18.0.1.1.0.3-py3-none-any.whl |
|---|---|
| Size | 32.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4730a68a78bcb0d69569b7eec4731952a4d39ef5b8f2858cd331284b4ed522aa
|
|
BLAKE2b-256 checksum How to use checksums |
cac60159665a50cc510ff518acc7521dda2c18c781e09c4c50cdf8ea13bb4b8e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|