Source connector

Adobe Commerce (Magento) connector

Adobe Commerce (Magento) integration for databases, warehouses and BI tools

Enterprise e-commerce catalog, orders, and customer data. Datrise captures Adobe Commerce (Magento) entities such as orders, products, customers, carts, and store views, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Adobe Commerce / Magento Open Source REST API (V1) authenticates with personal access token, incremental runs key on updated_at.

Of the 5 objects, 5 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `magento_orders`) with a schema derived from the Adobe Commerce (Magento) API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Adobe Commerce (Magento) pipeline page, and join the waitlist to get the Adobe Commerce (Magento) connector (ERP) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Adobe Commerce (Magento) data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
orders	magento_orders	Upsert by primary key, incremental on updated-at
products	magento_products	Upsert by primary key, incremental on updated-at
customers	magento_customers	Upsert by primary key, incremental on updated-at
carts	magento_carts	Upsert by primary key, incremental on updated-at
store views	magento_store_views	Upsert by primary key, incremental on updated-at

Adobe Commerce (Magento) API: setup facts for the connector

Verified against the vendor documentation on 2026-09-03. Unknown values are left blank rather than guessed.

API	Adobe Commerce / Magento Open Source REST API (V1)
Authentication	personal access token — A bearer admin or integration token in the `Authorization` header; third-party systems may instead use the OAuth 1.0a integration flow, and storefront JavaScript uses session auth.
Pagination	page — `searchCriteria[currentPage]` with `searchCriteria[pageSize]`; paginated results are capped at a default maximum of 300 items per page and list inputs at 20 entities.
Rate limit	Not published
Incremental cursor	updated_at — There is no since-parameter: an incremental read is a `searchCriteria` filter group on `field=updated_at` with `condition_type=gt` and the last watermark as `value`.
Webhooks	Not published
Bulk export	No
Deletes detectable	Not published

Official API reference

What bites when replicating Adobe Commerce (Magento)

Paginated REST and GraphQL results are capped at a default maximum of 300 items per page and endpoints taking a list of entities at 20, and both are server-side settings a connector cannot raise on its own.
Incremental reads have to be spelled out as `searchCriteria[filter_groups][0][filters][0][field]=updated_at` with `condition_type=gt` and a `YYYY-MM-DD HH:MM:SS` value — there is no simple modified-since parameter.
Adobe publishes no request-rate limit for the REST API itself; on Cloud infrastructure it is Fastly that enforces a rolling-window limit and returns HTTP 429, so achievable throughput depends on the hosting setup rather than the API.

Compare this against every other documented API

Popular destinations for Adobe Commerce (Magento)

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Adobe Commerce (Magento) connector FAQ

What Adobe Commerce (Magento) data does the connector extract?: 5 objects: orders, products, customers, carts and store views. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Adobe Commerce (Magento) integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Adobe Commerce (Magento) data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Adobe Commerce (Magento) → destination pair has its own page with the object-to-table mapping.

Related ERP sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Adobe Commerce (Magento) pipeline with guided onboarding

Join the waitlist to get priority access for Adobe Commerce (Magento) integrations with guided setup, schema-aware mapping, and production-grade incremental sync.