odxproxy-clientslisted
Install: claude install-skill terrakernel/odxproxy_claude_code_skills
# ODXProxy Clients
Help the user build applications against an Odoo ERP **through ODXProxy**, and
understand the target Odoo instance's data structure first so the code matches
reality.
## Mental model (read this first)
ODXProxy is a Rust reverse proxy exposing **one JSON-RPC 2.0 API** in front of
any number of Odoo instances. Apps call the proxy; the proxy calls Odoo's
`execute_kw`. Two facts drive almost every mistake:
1. **Two separate keys.** The proxy key goes in the `x-api-key` HTTP header
(client → proxy). The Odoo user key goes in the request body as
`odoo_instance.api_key` (proxy → Odoo). They are never the same value.
2. **HTTP 200 can still be an error.** Odoo logic/permission failures come back
inside a populated `error` object on a 200 response. Always inspect `error`
before reading `result`.
Endpoint: `POST /api/odoo/execute`. Only **9 actions** are allowed through:
`search_count`, `search`, `read`, `fields_get`, `search_read`, `create`,
`write`, `unlink`, `call_method` (arbitrary method — needs `fn_name`).
Minimal request body:
```json
{
"id": "req-1",
"action": "search_read",
"model_id": "res.partner",
"params": [[["is_company", "=", true]]],
"keyword": { "fields": ["id", "name", "email"], "limit": 20 },
"odoo_instance": { "url": "https://erp.example.com", "db": "prod", "user_id": 2, "api_key": "<odoo user key>" }
}
```
`params` = positional args to `execute_kw`; `keyword` = kwargs (`fields`,
`limit`, `offset`, `order`, `context