fix(connectors): rewrite Oxomi connector to the official Public API#383
Merged
Conversation
The previous Oxomi adapter used hallucinated paths (/catalog/search, /product/search, /document/search, /product/cross-selling), the wrong HTTP method (GET vs POST), and the wrong auth param (portalId instead of portal) — it could not work against the real service. Rewrite onto the official Oxomi Public API (/portals/api/...), JSON and documented, replacing the deprecated /service/json frontend API (sunset 2026-12-31). Full scope, 10 tools: product search + rich product/data, resolve-gtin, availability, brand/info, documents, datasheet render, and product-sync (changed/spx/update-sync-date). Auth is QUERY_AUTH (portal/user/accessToken in the query string); apiToken is injected only on the sync tools via $OXOMI_API_TOKEN. Endpoints, auth and request shapes verified live against portal 3001049 (product/data resolved a real product; brand/info and documents returned real data). Adds oxomi.live.spec.ts (static + opt-in live checks).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The existing Oxomi adapter was broken: hallucinated paths (
/catalog/search,/product/search,/document/search,/product/cross-selling), wrong HTTP method (GET vs POST), and wrong auth param (portalIdvs the API'sportal). This rewrites it onto the official Oxomi Public API (/portals/api/...) — JSON, documented — replacing the deprecated/service/jsonfrontend API (Oxomi sunsets it 2026-12-31).Scope (10 tools)
oxomi_search_products(v2 search),oxomi_get_product_data(rich blocks: images, attachments, prices, pages, availability…)oxomi_resolve_gtin,oxomi_product_availabilityoxomi_get_brand_info,oxomi_list_documents,oxomi_render_datasheetoxomi_sync_products_changed,oxomi_get_product_spx,oxomi_update_sync_dateAuth
QUERY_AUTH—portal/user/accessTokenin the query string (verified).apiTokeninjected only on the sync tools via$OXOMI_API_TOKEN.Verification (live, portal 3001049)
product/dataresolved a real product;brand/infoanddocumentsreturned real data;resolve-gtinOK.product-searchand per-block data are permission-gated on the token (Oxomi-side config, not a connector defect).validate-adapters: 183/183 pass. Addsoxomi.live.spec.ts(static always-on + opt-in live).