03 · Feeds · Open source

Agentic Commerce REST API for Magento 2

angeo/module-openai-product-feed-api

A REST layer over your product data — endpoints for feeds, products and promotions — for integrations that need to pull rather than wait for a scheduled file.

v2.0.0RESTAuthenticatedMIT
# install $ composer require angeo/module-openai-product-feed-api $ bin/magento setup:upgrade # create an integration token in Admin → System → Integrations

Free and MIT-licensed. No licence key, no account, no telemetry.

What it does

Four things worth knowing before you install.

Six endpoints, pull instead of push

Feeds, products with pagination and variants, and promotions — so a partner or internal service can request current data on demand rather than parsing the last generated file.

Authenticated end to end

Every route requires authentication. Earlier versions exposed anonymous webapi routes; that was fixed in 2.0.0 and no anonymous surface remains.

Promotions mapped to spec

Discounts and promotional pricing mapped to the fields the protocol defines, rather than left as raw Magento rule data a consumer has to interpret.

Runs with or without the feed module

Pairs with the file-based feed generator, or stands alone if a pull integration is all you need.

Upgrade if you are below 2.0.0. Versions before 2.0.0 exposed routes without authentication. This is a security fix, not a feature release.

Requirements

MagentoOpen Source / Adobe Commerce 2.4.x
PHP8.2+
AuthMagento integration tokens
Endpoints6 ACP REST endpoints
LicenceMIT

Questions

Do I need this if I already generate the feed file?

Only if something needs to pull data on demand. For submitting a catalogue to ChatGPT Shopping, the file-based feed module is sufficient.

How is access controlled?

Bearer-token authentication on every route. Feeds are persisted in the database rather than regenerated per request, and a PATCH-as-POST bridge keeps it compatible with Magento’s webapi routing.

Does it expose customer or order data?

No. The endpoints cover catalogue and promotion data only.

Is it rate limited?

Rate limiting is left to your web server or CDN, where it belongs, rather than being reimplemented inside the module.

Works with

Each module is independent, but these three are the ones most often installed alongside it.

Not sure whether you need this one?

Run the free scanner on your domain, or install the CLI audit. Both report which signals your store currently fails, so you install only what closes a real gap.