Before you connect your Magento 2 store to Elovate, please read this article first:
Required Magento 2 patches and make sure you have your API key created.
First time setup
If you have created your Elovate trial account, you will be redirected to the connection page right away.
Website url: enter the full url of your website, eg: https://www.elovate.io
What is the base language?: choose the base language of your store. Elovate will detect this by default
Webshop software: choose your webshop software, eg: Magento 2
API key: the API key you have created using this article
Click om the 'Connect' button to verify if your API key is valid. If valid, click on 'Save Connection' to save your connection.
Once your connection has been setup, Elovate will import all the needed data from your Magento 2 store.
IP whitelisting
Please note: if you have an IP restriction on your Magento environment, please make sure to whitelist the following IP-addresses:
168.119.238.80
159.69.3.130
167.235.27.69
Connect your Magento 2 store to Elovate
Before you can connect your Magento store to Elovate, you need to create an API key. With this key, Elovate can communicate with your Magento store en run all the needed syncs.
Login to your Magento backend
Go to System > Integrations
Click on the button on the top right: Add New Integration
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: All
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.
Important note
Since Magento 2.4.4, you need to explicit allow the use of bearer tokens. In order to allow this within your Magento installation, follow the steps below:
Go to Stores > Configuration > Services > OAuth
Open the tab Consumer Settings
Change the option Allow OAuth Access Tokens to be used as standalone Bearer tokens to Yes