Bruxel modules

Connect Bruxel with your store, your ERP and your other systems

Bruxel integrates through its public API, signed webhooks and a module for Adobe Commerce, so your systems read and write without anyone having to check in.

What it solves

A catalog that only lives on a screen forces someone to copy data between systems. With the API and webhooks, your store or your ERP finds out when something changes and reads the product as it is today.

  • A REST API with per-organization keys, scoped permissions and idempotency on the operations that charge credits.
  • Webhooks signed with a secret, with retries, a log of every delivery and “Resend”.
  • Bruxel_Sync for Adobe Commerce and Magento Open Source 2.4.7 to 2.4.9: the store sends its products and Bruxel returns the published content, with a dry-run mode before writing.

What it looks like

Bruxel's webhooks screen with demo addresses, the events they listen to and their last success or error.
Notifications to your systems, in Channels → Webhooks. · Demo data

Who it is for

  • Technology teams that connect the catalog to their ERP, PLM or store.
  • Adobe Commerce stores that want Bruxel's content on the product page.
  • Companies that want their team and suppliers to sign in through their own subdomain, such as pim.yourcompany.com.

What it needs

  • Creating API keys and webhooks is for administrators. The key and the secret are shown only once.
  • The Adobe Commerce module is installed with Composer by someone with technical access to the store.
  • A custom domain costs 100 credits a month and, for now, the Bruxel team sets it up.

Its guides

Read more: Bruxel integrations: public API, webhooks, Adobe Commerce and custom domain

Try it with your own catalog.

Connect Bruxel with your store, your ERP and your other systems · Bruxel