OdooWiki OCA HUB

EDI endpoint

edi_endpoint_oca folder_open OCA/edi-framework open_in_new
Uncategorised License: LGPL-3

Base module allowing configuration of custom endpoints for EDI framework.

auto_awesome What this module does

AI-generated from the code · Odoo 19.0

Lets you configure custom web endpoints that receive EDI files and automatically turn them into EDI exchange records, all managed from a dedicated EDI Endpoints menu.

This module connects the generic endpoint framework with the EDI framework, so incoming HTTP requests can be captured as EDI exchange records.

  • A new "EDI Endpoints" menu (under the EDI configuration menu) lists all endpoints. Each endpoint is linked to an EDI backend type, an EDI backend and an exchange type, and can be searched or grouped by these.
  • On an endpoint form you get an "Exchanges" button that opens the exchange records generated through that endpoint.
  • The execution mode "Create exchange record" stores the raw incoming request body as an exchange record and replies with a queued status, without needing custom code per endpoint.
  • On the EDI backend form, a new "Endpoints" tab shows how many endpoints are configured and a "Manage endpoints" button opens the list filtered on that backend.
  • Business rules: backend and exchange type are mandatory before an endpoint can be used; the exchange type must belong to the same backend type as the endpoint; a backend that still has active endpoints cannot be archived.
  • Exchange records now show the endpoint they came from, and consumer documents (such as related business records) can trace back to the origin endpoint.
  • Access is limited to EDI managers, and endpoints follow multi-company rules.

Depends on

base_ediedi_core_ocaendpoint

Required by other modules

edi_sale_endpointedi_sale_order_import_ubl_endpoint
Models and fields (5)
  • edi.backend · extends an existing modelendpoint_ids (Endpoints), endpoints_count
  • edi.endpoint · new modelexec_mode, backend_id, backend_type_id, exchange_type_id
  • edi.backend.type · extends an existing modelendpoint_ids (Endpoints)
  • edi.exchange.record · extends an existing modeledi_endpoint_id (Endpoint)
  • edi.exchange.consumer.mixin · extends an existing modelorigin_edi_endpoint_id (EDI origin endpoint)

Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 5 confirmed, 4 with no information of 9 versions.

terminal Installation and usage

OCA documentation · Odoo 19.0

Configuration

Source · Odoo 19.0

Go to "EDI -\> Config -\> Endpoints".

Exec modes

Each endpoint must pick an "Exec mode" that decides how the incoming request is turned into work for the EDI framework:

  • Create exchange record (default): persists the raw HTTP body as a new exchange record on the configured backend / exchange type and returns {"status": "queued", "id": <identifier>} with HTTP 200. Use this for "receive and queue" endpoints — no per-endpoint code snippet is required, and request validation (e.g. JSON Schema) is handled by the endpoint mixin before the handler runs.
  • Execute code: runs the user-provided code snippet, giving full control over how the request is processed and what is returned.

No verified information in OCA: Installation, Usage.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.