Odoo 19.0 Community · Persistent

account_edi_proxy_client.user: fields, relations and API

The account_edi_proxy_client.user model ("Account EDI proxy user") is a persistent model declared by the Proxy features for account_edi module, then extended by 3 other modules. It exposes 16 fields, 10 of them declared directly on the model; 6 fields from other models point to it. Below you will find every field with its technical name, type, label and relations, followed by an Odoo 19 JSON-2 API call.

View source code Search another model

Model identity

Technical name: account_edi_proxy_client.user
Label: Account EDI proxy user
Type: Persistent (models.Model)
SQL table: account_edi_proxy_client_user
Origin module: Proxy features for account_edi (account_edi_proxy_client)
Extended by: account_peppol, account_peppol_response, l10n_fr_pdp

Model fields

10 own fields, 0 inherited from mixins and 6 automatic ORM fields. Click a name to get a direct link to that field.

Hide inherited fields

16 of 16 fields shown

Technical name	Label	Type	Details
active	Active	`boolean`
company_id	Company	`many2one` → res.company	required
edi_identification	Edi Identification The unique id that identifies this user, typically the vat	`char`	required
edi_mode	EDI operating mode	`selection`	Values: `prod` (Production mode), `test` (Test mode), `demo` (Demo mode)
id_client	Id Client	`char`	required
is_token_out_of_sync	Token Out of Sync This field is used to indicate that the edi user token is out of sync with the proxy server. It is set to True when the token needs to be refreshed or updated.	`boolean`
private_key_id	Private Key The key to encrypt all the user's data	`many2one` → certificate.key	required
proxy_type	Proxy Type	`selection`	required
refresh_token	Refresh Token	`char`
token_sync_version	Token Sync Version	`integer`
create_date	Created on	`datetime`	read-onlyautomatic
create_uid	Created by	`many2one` → res.users	read-onlyautomatic
display_name	Display Name	`char`	read-onlycomputedautomatic
id	ID	`integer`	read-onlyautomatic
write_date	Last Updated on	`datetime`	read-onlyautomatic
write_uid	Last Updated by	`many2one` → res.users	read-onlyautomatic

Relations

Models linked from this model

certificate.key: private_key_id
res.company: company_id

Fields of other models pointing here

pdp.config.wizard: account_peppol_edi_user
pdp.registration: edi_user_id
peppol.config.wizard: account_peppol_edi_user
peppol.registration: edi_user_id
res.company: account_peppol_edi_user
res.config.settings: account_peppol_edi_user

Reading this model through the API

Odoo 19 JSON-2 API call reading the first five records with real fields of the model. Replace the instance, database and API key with your own.

curl

curl -X POST "https://your-instance.odoo.com/json/2/account_edi_proxy_client.user/search_read" \
  -H "Authorization: bearer $ODOO_API_KEY" \
  -H "X-Odoo-Database: your-db" \
  -H "Content-Type: application/json" \
  -d '{"domain":[],"fields":["company_id","edi_identification","id_client","private_key_id","proxy_type"],"limit":5}'

Python (requests)

import requests

BASE_URL = "https://your-instance.odoo.com/json/2"
headers = {"Authorization": f"bearer {API_KEY}", "X-Odoo-Database": "your-db"}

res = requests.post(
    f"{BASE_URL}/account_edi_proxy_client.user/search_read",
    headers=headers,
    json={"domain": [], "fields": ["company_id","edi_identification","id_client","private_key_id","proxy_type"], "limit": 5},
)
res.raise_for_status()
print(res.json())

External API access requires Odoo's Custom plan.
XML-RPC and JSON-RPC will be removed in Odoo 22 (fall 2028): use JSON-2.
The access rights and record rules of the key's user apply.

Cite this tool

Writing a tutorial, internal documentation or a forum answer? Copy this link to send your readers to the up-to-date reference.

<a href="https://aidoo.ai/en/outils/explorateur-modeles-odoo/account_edi_proxy_client-user">account_edi_proxy_client.user (Odoo 19.0)</a>

Sources

Data verified on September 23, 2026 · Odoo 19.0 Community

Have an Odoo project, or want to put your ERP to work with AI? Let's talk

Implementation, custom module development, connecting Claude or ChatGPT to your data: tell us about your context and we will reply within 24 business hours.