商品詳細は英語で表示されます。翻訳は近日公開予定です。
簡単な事実
- 価格
- $349.00 USD
- Odoo のバージョン
- 17, 18, 19
- セットアップ時間
- 20160分
- ライセンス
- ワンタイム永続
- 言語
- 11 言語
一回購入
REST API & Webhooks Toolkit
Secure, documented REST API and outbound webhooks for any Odoo model — built, installed, and supported by ECOSIRE for Odoo 17/18/19.
$349.00USD
今すぐのお支払いはありません。これはチームへの見積もり依頼を送信します。価格と次のステップをメールでご案内します。
主な機能
Auto-generated versioned REST endpoints (GET/POST/PATCH/DELETE) for each selected Odoo model, e.g. /api/v1/res.partner, mapped to ORM search_read, create, write and unlink
Long-lived API token authentication plus an OAuth2 client-credentials flow, with per-token expiry and revocation from a dedicated settings view
Per-token scopes that restrict access to specific models and actions (read-only, write, delete) so each integration gets least-privilege credentials
Access is enforced through Odoo's native ir.model.access.csv and record rules — endpoints run as a real user (auth='user'), never bypassing security
Outbound webhooks on record create/write/unlink events, wired via ORM overrides and base.automation, targeting your external URLs
HMAC-SHA256 signed webhook payloads with a shared secret so receivers can verify authenticity and reject spoofed calls
Configurable QWeb/Jinja-style payload templates per webhook to shape the JSON body and include only the fields a downstream system needs
Automatic retry with exponential backoff and a persisted delivery log (status, attempts, response) for every outbound webhook
Live Swagger/OpenAPI 3 documentation generated from enabled endpoints, with in-browser try-it-out and auth support
Per-endpoint rate limiting (requests per minute per token) to shield the Odoo worker pool from abusive or runaway clients
Structured request/response logging with status code, latency, caller token, and payload size for auditing and debugging
Field-level allow-lists per model so sensitive columns (cost, salary, internal notes) are never exposed even if the model is published
Pagination, filtering, and sorting on collection endpoints using Odoo domain-style query parameters (limit, offset, order, domain)
Consistent JSON error envelope with proper HTTP status codes (400/401/403/404/429/500) instead of raw Odoo tracebacks
CORS configuration and optional IP allow-listing for browser-based and server-to-server clients
Compatible with Odoo 17, 18 and 19 on Community and Enterprise, installed as a standard addon with no core patching
この製品について
Odoo ships a capable XML-RPC and JSON-RPC layer, but modern integration teams expect clean REST — predictable URLs, JSON bodies, bearer tokens, OpenAPI docs, and event-driven webhooks. Bridging that gap by hand means writing controllers, wiring authentication, hardening record-level access, and re-testing on every Odoo upgrade. The REST API & Webhooks Toolkit is a net-new module that ECOSIRE builds, installs, and supports for you, turning your Odoo instance into a first-class integration platform.
REST API & Webhooks Toolkitを選ぶ理由
Auto-generated versioned REST endpoints (GET/POST/PATCH/DELETE) for each selected Odoo model, e.g. /api/v1/res.partner, mapped to ORM search_read, create, write and unlink
Long-lived API token authentication plus an OAuth2 client-credentials flow, with per-token expiry and revocation from a dedicated settings view
Per-token scopes that restrict access to specific models and actions (read-only, write, delete) so each integration gets least-privilege credentials
Access is enforced through Odoo's native ir.model.access.csv and record rules — endpoints run as a real user (auth='user'), never bypassing security
Outbound webhooks on record create/write/unlink events, wired via ORM overrides and base.automation, targeting your external URLs
HMAC-SHA256 signed webhook payloads with a shared secret so receivers can verify authenticity and reject spoofed calls
This is a BUILD-TO-ORDER engagement, not an instant apps.odoo.com download. After purchase, an ECOSIRE Odoo engineer scopes the exact models, fields, and events you need to expose, then delivers a production-ready custom module (its own __manifest__.py, controllers, models, security rules, and views) tailored to your data model and hardened for your Odoo edition. Typical delivery is 2–4 weeks depending on the number of models and integration targets.
At its core the toolkit auto-generates versioned REST endpoints (for example GET/POST/PATCH/DELETE /api/v1/<model>) over the models you choose. Requests flow through Odoo's http.Controller layer with auth='user' so every call runs inside a real Odoo session and honors your existing ir.model.access.csv rules and record rules — a token cannot read or write anything the mapped user is not already allowed to touch. Authentication supports long-lived API tokens and an OAuth2 client-credentials flow, with per-token scopes so a warehouse app can be limited to stock.picking while a CRM sync only sees crm.lead.
Outbound webhooks close the event loop. Using Odoo's ORM overrides and base.automation / automated actions, the module fires signed HTTP POST callbacks to your endpoints when records are created, written, or unlinked — new sale.order, confirmed account.move, updated res.partner — with configurable payload templates, HMAC signatures, retry-with-backoff, and a delivery log so nothing is silently lost. Every inbound and outbound call is captured with status code, latency, and payload size, and each endpoint carries its own rate limit to protect the server.
Developers get a live Swagger/OpenAPI 3 specification generated from the enabled endpoints, so your integrators can explore, authenticate, and test straight from the browser. The module is built cleanly on the standard framework — no core patching — so it installs alongside your other apps and survives upgrades. ECOSIRE supports Odoo 17, 18, and 19, on Community or Enterprise, and hands over full source plus documentation and a support window so your team owns and can extend the result.
得られるもの
- Complete custom Odoo module source (models, http.Controller endpoints, security CSV + record rules, views, and __manifest__.py) scoped to your models and Odoo version
- Configured REST endpoints for your agreed models plus token/OAuth2 credentials provisioned in a staging environment
- Configured outbound webhooks for your agreed record events, wired to your target URLs with signing secrets set up
- Auto-generated Swagger/OpenAPI 3 specification file plus a hosted docs page for your integrators
- Integration guide and runbook covering authentication, endpoints, webhook payloads, retry behavior, and error codes
- A live handover / training session for your developers and admins, walking through configuration, token management, and the delivery log
- Installation and deployment on your instance (Community or Enterprise, self-hosted or Odoo.sh) with post-install smoke tests
- Post-delivery support window for bug fixes and questions, plus a maintenance/upgrade path across Odoo 17, 18 and 19
これは誰のためのものですか
Integration Developer / API Consumer
Engineers wiring Odoo into external apps — mobile clients, e-commerce fronts, partner portals — who want clean REST, bearer tokens, and an OpenAPI spec instead of hand-rolling XML-RPC calls and reverse-engineering field names.
Systems Integrator / Consultant
Odoo partners and integrators delivering multi-system projects who need a reliable, security-aware REST + webhook layer they can configure per client rather than rebuilding controllers and auth for every engagement.
IT / Automation Lead
In-house technical owners connecting Odoo to iPaaS tools, warehouse scanners, or accounting systems, who need event-driven webhooks, per-token rate limits, and full request logging to keep integrations observable and safe.
インストールの概要
ECOSIREからダウンロード
ecosire.com でライセンスを購入し、アカウント ダッシュボードから REST API & Webhooks Toolkit モジュールの ZIP をダウンロードします。
Odoo にアップロードする
ZIP をサーバー上の Odoo カスタム アドオン フォルダーに抽出します (または、[アプリ] > [Odoo.sh / runbot のファイルからインストール] を介してアップロードします)。
モジュールをインストールする
開発者モードをアクティブにし、アプリを開き、「アプリリストの更新」をクリックして、「REST API & Webhooks Toolkit」を検索し、「インストール」を押します。
設定を構成する
新しいメニューを開き、ECOSIRE ライセンス キーを貼り付け、外部認証情報 (Shopify、Amazon、Stripe など) を接続して保存します。
検証して公開する
組み込みの接続テストを実行し、最初の 10 レコードを同期し、定期的な cron をスケジュールします。何か問題が発生した場合はサポートにお問い合わせください。
REST API & Webhooks Toolkit の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| REST endpoints with clean JSON (not raw RPC method calls) | 付属 | 部分的なサポート | 部分的なサポート | |
| Token + OAuth2 authentication with per-token scopes | 付属 | 部分的なサポート | 部分的なサポート | |
| Outbound webhooks on record create/write/unlink events | 付属 | 部分的なサポート | 部分的なサポート | |
| Signed payloads (HMAC) + retry with delivery log | 付属 | 含まれていない | 含まれていない | |
| Auto-generated Swagger/OpenAPI 3 documentation | 付属 | 含まれていない | 部分的なサポート | |
| Per-endpoint rate limiting and request logging | 付属 | 含まれていない | 部分的なサポート | |
| Enforces existing ir.model.access.csv + record rules | 付属 | 部分的なサポート | 部分的なサポート | |
| Built and hardened for your exact models on Odoo 17/18/19 | 付属 | 部分的なサポート | 含まれていない | |
| Full source handover, docs, training + support window | 付属 | 部分的なサポート | 含まれていない |
REST API & Webhooks Toolkit に関するよくある質問
How long until the module is delivered and installed?
This is a build-to-order engagement, not an instant download. After purchase an ECOSIRE engineer scopes the exact models, fields, and events you want exposed, then builds and delivers a production-ready custom module. Typical lead time is 2–4 weeks depending on how many models and webhook targets are in scope. We install it in staging first, run smoke tests, then deploy to production with you.
What support and updates are included after delivery?
Every engagement includes a post-delivery support window for bug fixes and configuration questions, plus a documented upgrade path. Because the module is built cleanly on the standard framework (controllers, ORM, base.automation, ir.model.access.csv) with no core patching, it moves across Odoo 17, 18 and 19 predictably. You receive full source code, so your team can extend endpoints and webhooks independently, and we offer optional ongoing maintenance retainers.
Isn't Odoo's built-in XML-RPC/JSON-RPC enough?
For simple back-office scripting, sometimes. But XML-RPC and JSON-RPC expose raw model methods, have no per-token scoping, no OpenAPI docs, no rate limiting, and no outbound webhooks. This toolkit adds a REST surface with bearer/OAuth2 auth, per-endpoint limits, signed event webhooks, and generated Swagger docs — the things modern integration teams and iPaaS tools expect.
How is security handled — can a token access everything?
No. Endpoints run as a real Odoo user via auth='user', so every call is filtered through your existing ir.model.access.csv and record rules — a token can never read or write records the mapped user cannot. On top of that we add per-token scopes (which models and actions), optional field-level allow-lists, token expiry/revocation, IP allow-listing, and per-endpoint rate limits.
Which Odoo versions and editions are supported?
We support Odoo 17, 18 and 19, on both Community and Enterprise, self-hosted or on Odoo.sh. During scoping we confirm your exact version and edition and build the module against it, including any edition-specific models you want exposed. If you later upgrade, the handover includes a version-migration path.
Can webhooks fire on custom events and reach any external system?
Yes. Outbound webhooks are wired through ORM create/write/unlink overrides and Odoo automated actions, so they can trigger on record creation, updates, stage changes, or your own conditions. Each webhook has a configurable JSON payload template, an HMAC signature for verification, and retry-with-backoff, so it can safely deliver to any HTTPS endpoint — iPaaS, a partner API, or your own microservice — with a full delivery log.
関連モジュール
見積もりを依頼
REST API & Webhooks Toolkit
Secure, documented REST API and outbound webhooks for any Odoo model — built, installed, and supported by ECOSIRE for Odoo 17/18/19.
- Auto-generated versioned REST endpoints (GET/POST/PATCH/DELETE) for each selected Odoo model, e.g. /api/v1/res.partner, mapped to ORM search_read, create, write and unlink
- Long-lived API token authentication plus an OAuth2 client-credentials flow, with per-token expiry and revocation from a dedicated settings view
- Per-token scopes that restrict access to specific models and actions (read-only, write, delete) so each integration gets least-privilege credentials
- Access is enforced through Odoo's native ir.model.access.csv and record rules — endpoints run as a real user (auth='user'), never bypassing security