eMAG Marketplace

eMAG Marketplace

This connector uses the eMAG Marketplace API (API 3, documentation v4.5.2) for sellers on eMAG Romania, Bulgaria and Hungary (and the Fashion Days marketplaces on the same API): products and offers, prices and stock, orders, AWBs (shipping labels), return requests (RMA), categories and characteristics, VAT and handling time values, campaigns and invoices.

Setup (about 10 minutes, plus eMAG's IP check)

1. In the eMAG Marketplace seller area, use (or have the account owner create) a user with API rights.
2. IP whitelisting: eMAG only accepts API calls from IP addresses you registered with them. Send eMAG Marketplace support the public IP address this connector calls from (on a self-hosted installation the address of your server; on AnythingMCP Cloud the fixed IPv4 address 104.248.242.235, from which Cloud makes every call). Until then every call answers You are not allowed to use this API.
3. Set EMAG_API_HOST to the host of your platform, without a path: https://marketplace-api.emag.ro (Romania), https://marketplace-api.emag.bg (Bulgaria), https://marketplace-api.emag.hu (Hungary), https://marketplace-ro-api.fashiondays.com or https://marketplace-bg-api.fashiondays.com (Fashion Days). Each platform is a separate account: one connector per country.
4. Put the API user in EMAG_USERNAME and its password in EMAG_PASSWORD (HTTP Basic auth).
5. Install and run emag_marketplace_list_vat_rates.

How the API works: every resource is called as POST <resource>/read, count or save. Reads take their filters and paging as top-level fields (currentPage, itemsPerPage at most 100); saves take a list of objects that the connector wraps in data. All reads here are marked read-only even though they are POST. Every answer is {"isError": false, "messages": [], "results": [...]}; isError: true is reported as a failed call with the messages. Exception: saving a new product with a documentation problem answers isError: true but the offer is still saved, so read it back with emag_marketplace_list_product_offers.

Products and offers: emag_marketplace_list_product_offers and emag_marketplace_count_product_offers (filter by status, validation_status, offer_validation_status, part number or PNK). An offer is on sale only with stock > 0, status 1, offer_validation_status 1 and validation_status 3, 9, 11 or 12. emag_marketplace_find_products_by_ean tells whether a product already exists, so you attach your offer to it. To create a product read the category with emag_marketplace_list_categories (with id for its characteristics; emag_marketplace_count_categories for the number of pages), the VAT ids with emag_marketplace_list_vat_rates and handling times with emag_marketplace_list_handling_times, then call emag_marketplace_save_product_offers. Price and stock changes of existing offers: emag_marketplace_update_offers (light offer API) or emag_marketplace_update_offer_stock for stock only. emag_marketplace_save_measurements stores dimensions and weight.

Orders: emag_marketplace_list_orders and emag_marketplace_count_orders (status 1 new, 2 in progress, 3 prepared, 4 finalized, 0 canceled, 5 returned). The flow: new order > emag_marketplace_acknowledge_order (status 2) > emag_marketplace_save_order with status 3 (prepared) > AWB with emag_marketplace_create_awb > status 4 (finalized). emag_marketplace_save_order needs the whole order as read, with only the changed fields different. Vouchers applied to an order are part of the order data (vouchers, product_voucher_split); there is no separate voucher resource. Documents: emag_marketplace_list_order_attachments and emag_marketplace_save_order_attachments (invoice type 1, warranty type 3).

Shipping (AWB): emag_marketplace_list_courier_accounts, emag_marketplace_list_addresses (pickup and return addresses), emag_marketplace_list_localities (locality ids for sender and receiver), emag_marketplace_list_awb_packages and emag_marketplace_get_order_volumetry (package sizes), then emag_marketplace_create_awb. Read it back with emag_marketplace_get_awb and print it with emag_marketplace_get_awb_pdf (A4, A5, A6) or emag_marketplace_get_awb_zpl. emag_marketplace_unlock_courier frees the courier choice of an order.

Returns (RMA): emag_marketplace_list_returns and emag_marketplace_count_returns (request_status 2 new, 3 acknowledged, 6 received, 7 finalized, 4 refused, 5 canceled); emag_marketplace_save_return moves a return to its next status (2 > 3 or 5, 3 > 6 or 5, 6 > 4 or 7).

Campaigns: emag_marketplace_list_campaigns (rules and deadlines), emag_marketplace_list_campaign_categories (when the categories are restricted), emag_marketplace_list_campaign_eligible_offers (your offers with the maximum campaign price), emag_marketplace_propose_campaign_offers, emag_marketplace_get_offer_campaign_badges and emag_marketplace_check_smart_deals_price.

Invoices: emag_marketplace_list_invoice_categories, emag_marketplace_list_invoices (what eMAG bills you) and emag_marketplace_list_customer_invoices (invoices on your orders).

Writes: confirm first. Prices, stock, order status, AWBs, returns and campaign proposals act on the live store and on real couriers. Before each write show the user what changes (offer ids with old and new price or stock, order and new status, AWB data) and wait for a yes. Save calls take at most 50 entities (10 to 50 recommended).

Reading the data: id on offers is your own seller product id (ext_id); part_number_key (PNK) is eMAG's product key. Prices are without VAT in the platform currency (RON in Romania, EUR in Bulgaria since 1 January 2026, HUF in Hungary). Dates are YYYY-mm-dd HH:ii:ss in local time of the platform. Order date filters on count need both ends, at most one month apart.

Limits: 12 requests per second for orders, 3 per second for all other resources together; beyond that eMAG answers 429. At most 4000 input fields per request. Do not loop faster than needed.