Connecting Magento lets Elovate import your catalog, enrich content, and sync updates back to your store. Follow these sections in order:
Prerequisites & network allowlist
Create the Magento Integration (API key)
(Magento ≤2.4.2) Install required API patches
Enable bearer tokens (Magento ≥2.4.4)
Finish the connection in Elovate
Verify the first sync & what to expect
1) Prerequisites & network allowlist
Admin access to your Magento 2 backend & CLI (for patches).
Publicly reachable Magento (Elovate needs to call your API).
Firewall/IP allowlist (if you restrict access): allow these Elovate workers:
IPv4
168.119.238.80
159.69.3.130
167.235.27.69
IPv6
worker 1:
2a01:4f8:c0c:eb3a::/64
worker 2:
2a01:4f8:1c1e:a907::/64
platform:
2a01:4f8:1c1e:5007::/64
2) Create the Magento Integration (API key)
Next, add the following:
Integration Info > General > Name: the name of your integration, eg: Elovate
Integration Info > Current User Identity Verification > Your Password: your admin password
API > Available APIs > Resource Access:
Catalog
Inventory
Products
Mass Update Attributes
Edit Product Design
Categories
Edit Category Design
Customers
Customer Groups
Content
Elements
Pages
Save Page
Edit Page Design
Delete Page
Blocks
Widgets
Stores
Settings
All Stores
Configuration
Catalog Section
General Section
Attributes
Product
Attribute Set
Amasty: Layered Navigation (when available and in your subscription)
Pages
Brand Management
Click on the top right button (on the arrow), and click Save & Activate
A popup will open. In this popup, click on the top right button Allow
Copy the content of the field Access Token and add this into the API key field in Elovate.
Magefan blog module
If you have Magefan blogs and also want them in Elovate then please enable the following
Blog
Posts
Save
Categories
Save
Tags
Save
3) (Magento ≤2.4.2) Install required API patches
Magento has a historical REST quirk that can unset values at store‑view level. If you’re on 2.4.3 or higher, you don’t need these patches.
If you’re on 2.4.2, install only the Product API patch.
If you’re on below 2.4.2, install both patches.
Install via Composer
composer require elovate-app/magento-patches
Update your composer.json
(add under "extra"
):
"extra": { "magento-force": "override", "patches": { "magento/module-catalog": { "Magento 2 REST API patch for category API calls": "vendor/elovate-app/magento-patches/category-api/category_repository.patch", "Magento 2 REST API patch for product API calls": "vendor/elovate-app/magento-patches/product-api/product_repository.patch" } } }
Version rules
2.4.3+ → no patches needed
2.4.2 → keep only:
"Magento 2 REST API patch for product API calls": "vendor/elovate-app/magento-patches/product-api/product_repository.patch"
<2.4.2 → keep both product+category patches
Then deploy as usual (e.g. composer install
, cache flush, compile if required).
4) Enable bearer tokens (Magento ≥2.4.4)
Since Magento 2.4.4, you must explicitly allow bearer tokens:
Stores → Configuration → Services → OAuth → Consumer Settings
Allow OAuth Access Tokens to be used as standalone Bearer tokens → Yes
Save config, then flush cache.
5) Finish the connection in Elovate
In Elovate (you’ll land here after signup, or go to Configuration → Settings):
Website URL: full frontend URL (e.g.
https://www.example.com/
).Base language: Elovate will auto-detect; confirm it’s correct.
Webshop software: select Magento 2.
API key: paste the Access Token from step 2.
Click Connect → if valid → Save Connection.
If your Magento has IP restrictions, make sure you’ve allowlisted the Elovate IPs (see step 1). A failed “Connect” usually indicates token/URL/firewall issues.
6) Verify the first sync & what to expect
Once saved, Elovate will start its initial import:
Products, Categories, Attributes, Pages, Blocks appear in Store data.
In Dashboard, you’ll see Import from Magento activity.
Sync to Magento only starts once you perform updates from Elovate (imports are read; syncs are write-back).
Health checks if something’s off
Connection fails → recheck token, base URL, bearer token setting (2.4.4+), firewall IPs, patches (≤2.4.2).
Attributes missing or “unset” behavior on store views → confirm the correct patch is applied (see step 3).
Slow or queued syncs → depends on Magento performance; watch Dashboard → Sync to Magento for queue length.
Quick reference (copy/paste)
Magento API token: System → Integrations → Add → API: All → Save & Activate → Allow → Access Token
Bearer tokens (2.4.4+): Stores → Configuration → Services → OAuth → Allow… as standalone Bearer tokens = Yes
Patches:
composer require elovate-app/magento-patches
+"magento-force":"override"
+ product/category patch paths (per version)IP allowlist:
IPv4:
168.119.238.80
,159.69.3.130
,167.235.27.69
IPv6:
2a01:4f8:c0c:eb3a::/64
,2a01:4f8:1c1e:a907::/64
,2a01:4f8:1c1e:5007::/64
If you want, I can now update the Step 2 draft directly in your knowledge center voice (short intro + structured steps), or jump to Step 3 — Add new users.