Oxomi Product & Media Portal

This connector uses the official Oxomi Public API (/portals/api/...) — JSON, documented, and not the deprecated /service/json frontend API (which Oxomi sunsets on 2026-12-31).

Credentials

Enter these when importing the connector; they are injected as query parameters on every call:

• OXOMI_PORTAL_ID — your numeric portal id (e.g. 3001049)
• OXOMI_USER — your Oxomi portal user (set a non-empty value; used for profile-scoped access)
• OXOMI_ACCESS_TOKEN — the portal API access token (Portal-Einstellungen → API)
• OXOMI_API_TOKEN — the API-Token ID, required ONLY by the product-sync tools (oxomi_sync_products_changed, oxomi_get_product_spx, oxomi_update_sync_date). Leave unset if you don't use sync.

Permissions matter

Each Oxomi access token is granted a specific set of API permissions and product query blocks on the portal side. If a call returns 403 Missing permission: <x> or resolves a product but returns empty queries, ask your Oxomi admin to enable that permission/block for the token. product/data resolution, resolve-gtin, brand/info and documents are commonly enabled; product-search and individual data blocks (prices, attachments, …) often must be granted explicitly.

Typical workflows

• Product lookup: oxomi_search_products (text/code/GTIN) → take itemNumber + supplierNumber → oxomi_get_product_data with the queries you need (e.g. attachments, product-images, prices, pages).
• Barcode: oxomi_resolve_gtin → supplierNumber + itemNumber → oxomi_get_product_data.
• Documents/brand: oxomi_list_documents, oxomi_get_brand_info.
• Bulk/ETL: oxomi_sync_products_changed (incremental, continuationToken pagination) + oxomi_get_product_spx.

Products are identified by itemNumber + supplierNumber. Most content is German; pass a language code (e.g. en) where the supplier provides translations.