Connecting Magento to Elovate is straightforward. In most cases, you only need to create an integration in Magento, select the required API resources, copy the access token, and paste it into Elovate.
Essentials
In the Magento back-end
Go to System → Integrations
Click Add New Integration
Enter a name for the integration, for example Elovate
Enter your admin password under Current User Identity Verification
Open the API section and create the API with the following resources:
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
6. Click Save & Activate
7. In the popup, click Allow
8. Copy the Access Token
In Elovate
Click Add new connection
Fill in the following fields:
Website URL
Base language
Webshop software: Magento 2
Paste the access token into the API key field
Click Connect
Save the connection
Once the connection is saved, you're all set.
Only if needed
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.80159.69.3.130167.235.27.69
IPv6
worker 1:
2a01:4f8:c0c:eb3a::/64worker 2:
2a01:4f8:1c1e:a907::/64platform:
2a01:4f8:1c1e:5007::/64
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
(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).
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.
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.69IPv6:
2a01:4f8:c0c:eb3a::/64,2a01:4f8:1c1e:a907::/64,2a01:4f8:1c1e:5007::/64