| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 2081 |
| Technical Name |
hdk_rapidapi_integration |
| License | OPL-1 |
| Website | https://www.hamdek.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 2081 |
| Technical Name |
hdk_rapidapi_integration |
| License | OPL-1 |
| Website | https://www.hamdek.com |
Category pioneer · First RapidAPI-native module on the Odoo Apps Store
Built for RapidAPI Hub end-to-end: keys, hosts, GET mapping, fetch samples, upsert, scheduled sync—your ERP on-ramp into that ecosystem. Ecosystem scale & roles: next section.
Hamdek RapidAPI Integration
Integrate RapidAPI-style HTTP APIs with Odoo: store API keys, define GET endpoints, map JSON paths to Odoo fields, fetch sample responses, and sync records manually or on a schedule—with optional external ID upsert.
Flash reasons to install
- Repeatable runway: Connection → API → fetch sample → map → sync—same story every time you add a vendor.
- Catalog breadth: Tap Hub listings across AI, data, finance, HR, comms, geo—without hard-coding each vendor.
- Ops that sleeps: Upsert + optional cron—configure once, keep Odoo fresh without spreadsheet imports.
RapidAPI: muscle, reach, who it’s for
6M+ developers · 44,000+ API listings
A global API marketplace where teams find, test, and connect to tens of thousands of APIs. RapidAPI helped normalize catalog → trial → one key → ship.
This app is the first on the Odoo Apps Store purpose-built for that Hub flow—responses become Odoo records using X-RapidAPI-Key / X-RapidAPI-Host, not a pile of side scripts.
Who plays on RapidAPI? Still one screen, four roles.
API consumers
Search, try, and integrate public APIs. Hub corrals subscriptions with one key across many endpoints—less key sprawl, faster shipping.
API providers
Publish and optionally monetize APIs; track traction in a Provider Dashboard built for builders, not spreadsheets.
Enterprise
Enterprise Hub for governance across teams—internal APIs, policies, visibility. Names you know: IATA, Poly, Sun Life Financial (examples of enterprise adoption).
Environment admins
Own permissions, billing, and platform rules so dozens of projects don’t become dozens of shadow keys.
Why RapidAPI belongs next to Odoo
ERP holds master data and processes; RapidAPI is where external services live. This module is the handshake—business truth stays in Odoo instead of orphan exports.
What this module does in Odoo
Connects Hub JSON to any target model: host, path, query lines, and a mapping table from JSON paths to Odoo fields—including relations (Many2one / One2many) and images from URLs or base64. Step-by-step setup is in Workflow below; deeper field behaviors are under Key Features.
Key Features
Query parameters
Ordered key / value lines per API; values are URL-encoded when building the GET URL.
Relations & extras
Many2one search/create, One2many child rows, and extra fields on related records (e.g. job location / partner address, images).
Binary & URLs
Binary/Image fields accept base64, data URLs, or http(s) links to images (downloaded safely; optional attachment on the record).
Upsert
Optional external ID path + field: update existing records when the key matches, otherwise create.
Use Cases
Business outcomes you can support by pulling live data and services into Odoo—one repeatable flow for each integration.
Hiring & talent
Keep vacancies and candidate-facing information current from external job and talent feeds—less copy-paste, fewer stale postings.
Sales & CRM
Enrich accounts and leads with firmographics, signals, or ratings so reps open Odoo to useful context, not yesterday’s spreadsheet.
Operations & logistics
Bring in rates, availability, or tracking-style updates so dispatch and warehouse teams work from one system of record.
Finance & treasury
Refresh exchange rates, benchmarks, or reference data on a schedule so invoices and reports reflect the market you care about.
Marketing & content
Sync campaign stats, social signals, or content feeds so planning and reporting stay aligned with what’s live outside the ERP.
Product & catalog
Update descriptions, media, or specs from trusted external sources so ecommerce and sales teams sell what’s actually available.
Workflow
Install Hamdek RapidAPI Integration (requires base only). Then follow the steps below.
RapidAPI connection
Create a Connection and store your RapidAPI API key. Reuse it for one or more API endpoints.
API endpoint
Create an API: host, path, query parameters, target model, record JSON path, optional external ID for upsert.
Query parameters
Fetch sample & field mapping
Use Fetch Sample, then fill the mapping table: Odoo field, JSON path, and relation columns as needed.
Sample response
Field mapping
Field mapping guide
Sync & automation
Run Sync now or enable Include in scheduled sync and configure the RapidAPI job under Settings → Technical → Automation.
Support & Expert Services
admin@hamdek.com
www.hamdek.com
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module