E-commerce
Retail Express by Maropost
SaaS API (REST)
Managed auth, retries, and throttling
Export coverage
Know exactly what Vern pulls before you migrate.
Objects Vern extracts
Vern extracts the full set of queryable Retail Express by Maropost objects (52 total), including: Countries, Credit Note Items, Credit Notes, Currencies, Customer Delivery Addresses, Customer Logs, Customer Survey Segments, Customer Types, Customers, Freight Types, Inventory, Inventory Movement Logs, Loyalty Adjustment Reasons, Max Discount Rules, Order Fulfilments, Order Items, Order Payments, Orders, Outlets, Price Groups Fixed, Price Groups Standard, Product Attribute Values, Product Attributes, Product Barcodes, Product Details Log, Product Prices, Product Replenishment Methods, Product Types, Products, Purchase Order Items, Purchase Orders, Receipt Variance Reasons, Return Reasons, Shipment Types, Shipping Ports, Shipping Status, Stock Adjustment Reasons, Stock Receipts, Supplier Invoices, Supplier Return Item Source, Supplier Return Item Status, Supplier Return Reasons, Supplier Return Status, Supplier Returns, Suppliers, Transfer Items, Transfer Status, Transfer Types, Transfers, Users, Voucher Types, and Vouchers. 28 of these support incremental change tracking, so syncs pull only what changed.
Output schema
Normalized JSON per object with referential keys preserved, so the relationships between your user's records survive the import. Timestamps are returned in ISO 8601. Delivered as JSON or CSV, or loaded straight into your own application database or pushed to your API — whatever your product expects.
Where it can land
Your own application database (Postgres, MySQL), a direct push to your API or webhook, or JSON/CSV files, plus another e-commerce system (Adobe Commerce (Magento), Akeneo, Amazon Seller Partner) when a user is switching tools.
Source details
Built for the source type shown above, with extractor content refreshed from the collection record.
Managed by Vern
The details you normally have to build yourself.
Authentication
API key / access token. Your user pastes their Retail Express by Maropost API key once when they sign up; Vern stores it encrypted and attaches it to every request, handling header signing and retries so you never touch the raw credential.
Pagination
Vern detects and handles Retail Express by Maropost's paging model (cursor, page-number, or offset) internally and returns one consistent, de-duplicated result set — so you import a user's complete data without ever managing page tokens.
Rate limits and gotchas
Retail Express by Maropost enforces its own API rate limits. Vern queues and throttles requests internally so importing a new user's data never trips a 429 — even on a large account.
API-key sources rarely surface their true rate ceilings until you hit a 429 mid-import, and many silently cap page size. Vern throttles to stay under the limit and normalizes paging so a partial pull never lands a user in your product with missing data.
API quickstart
A cleaner way to extract without rebuilding source-specific plumbing.
View docs
Common questions
Can I keep a user's Retail Express by Maropost data in sync after the first import? Yes — 28 Retail Express by Maropost objects support incremental change tracking, so after the first full import Vern pulls only what changed on re-run.
Can I move a user from Retail Express by Maropost to Adobe Commerce (Magento)? Yes — Vern normalizes the Retail Express by Maropost data model into typed tables that map cleanly onto Adobe Commerce (Magento) and into your own product.
What does it cost to read the Retail Express by Maropost API? Retail Express by Maropost's own API access follows Retail Express by Maropost's pricing/plan; Vern is billed separately per import. Check Retail Express by Maropost's developer docs for their current limits.
