How To Create An Integration In Magento 2

What is magento 2 integration?

In computer science, Integration is a term that is commonly used when an application needs interacting with other applications for transferring data or triggering an action.

However, in Magento 2, integration is a definition for a third-party application that uses OAuth for authentication. It allows developers or administrators to define which resources (such as customers, orders, or catalog) the application can access.

As a Magento merchant, you can use the Magento back-end to create the integration manually or build a custom Magento extension to create that integration programmatically. 

Create integration in Magento 2 manually

Step 1: Go to System -> Integrations Menu.

Step 2:  Click add new integration to open a new integration form.

Step 3: Enter the integration name as the form in the above picture.

Step 4: Grant access to the API resources.

Step 5: Save to create a new consumer public & secret keys for integration.

Step 6: Activate integration for creating an access token for the external application.

After activating, we can see the integration detail in the picture below.

The access token after generating can be used by any API test tools (as swagger or postman) or any 3rd party applications. Our HexaSync Integration Platform used the same method for integrating Magento 2 eCommerce website with ERP systems like Acumatica and Infor CloudSuite Industrial as well.

The example below is a simple API request for retrieving all the subcategories under the default root category of the Magento 2 sample database.

curl -X GET "https://{{your_magento_url}}/rest/all/V1/categories?rootCategoryId=2&depth=1" -H  "accept: application/json" -H  "Authorization: Bearer 9qe33ln9ff7xfpkkzkat9tq2ekbx13cy"
Code language: JavaScript (javascript)

The JSON response data:

{  "id": 2,  "parent_id": 1,  "name": "Default Category",  "is_active": true,  "position": 1,  "level": 1,  "product_count": 1181,  "children_data": [    {      "id": 64,      "parent_id": 2,      "name": "What's New",      "is_active": true,      "position": 1,      "level": 2,      "product_count": 0,      "children_data": []    },    {      "id": 46,      "parent_id": 2,      "name": "Women",      "is_active": true,      "position": 2,      "level": 2,      "product_count": 0,      "children_data": []    },    {      "id": 37,      "parent_id": 2,      "name": "Men",      "is_active": true,      "position": 3,      "level": 2,      "product_count": 0,      "children_data": []    },    {      "id": 3,      "parent_id": 2,      "name": "Gear",      "is_active": true,      "position": 4,      "level": 2,      "product_count": 46,      "children_data": []    },    {      "id": 9,      "parent_id": 2,      "name": "Training",      "is_active": true,      "position": 5,      "level": 2,      "product_count": 6,      "children_data": []    },    {      "id": 7,      "parent_id": 2,      "name": "Collections",      "is_active": false,      "position": 5,      "level": 2,      "product_count": 13,      "children_data": []    },    {      "id": 55,      "parent_id": 2,      "name": "Promotions",      "is_active": false,      "position": 6,      "level": 2,      "product_count": 0,      "children_data": []    },    {      "id": 63,      "parent_id": 2,      "name": "Sale",      "is_active": true,      "position": 6,      "level": 2,      "product_count": 0,      "children_data": []    }  ]}
Code language: JSON / JSON with Comments (json)

Create an integration in magento 2 programmatically

Magento 2 manages integrations under Magento_Integration module.

By using MagentoIntegrationModelConfigBasedIntegrationManager class, we can create an integration with XML configuration files. It takes three main steps for getting this process done.

Creating a skeleton Module

Step 1. Create the module file structure.

Like any other of Magento 2 custom modules, The module for integration should be placed under magento_base_dir/app/code/{{vendor_name}}/{{module_name}} or under the magento_base_dir/vendors/ folder. In this example, we will place source code under. To make it simple, lets create under /app/code/{{vendor_name}}/{{module_name}} by running these commands.

cd mkdir -p app/code//{{vendor_name}}/{{module_name}}/etc/integrationmkdir -p app/code//{{vendor_name}}/{{module_name}}/Setup
Code language: JavaScript (javascript)

Note: In this post, we are going to use Beehexa as vendor and IntegrationManager as the module name.

Step 2. Define your module configuration file etc/module.xml

The etc/module.xml the file provides basic information about the module. Change directories to the etc directory and create the module.xml file. We must specify values for the following following information:

• Module name
• Module version
• Dependencies

Code language: HTML, XML (xml)

Because in the install script that we are going to add later in this tutorial, we call a class name MagentoIntegrationModelConfigBasedIntegrationManager. We have to add Magento_Integration

a dependency for our custom integration creator.

Step 3. Add your modules composer.json file

Composer is a dependency manager for PHP. You must create a composer.json file for your module so that Composer can install and update the libraries your module relies on. Then place the composer.json file in the modules root directory.

{    "name": "beehexa/integrationmanager",    "description": "",    "type": "magento2-module",    "version": "1.0.1",    "license": [      "MIT"    ],    "autoload": {      "psr-4": {        "Beehexa\IntegrationManager\": ""      },      "files": [        "registration.php"      ]    }  }
Code language: PHP (php)

For more information, see Create a component from the official Magento development documentation.

Step 4. Create a registration.php file

The registration.php registers the module with the Magento system. It must be placed in the modules root directory.

<h4>Step 5. Create an install class that will create integration when the module is installedh4><p>Change directories to your <code>Setupcode> directory. Create a <code>InstallData.phpcode> file that installs the integration configuration data into the Magento integration table.p><pre><code>namespace BeehexaIntegrationManagerSetup;use MagentoFrameworkSetupModuleContextInterface;use MagentoFrameworkSetupModuleDataSetupInterface;use MagentoIntegrationModelConfigBasedIntegrationManager;use MagentoFrameworkSetupInstallDataInterface;class InstallData implements InstallDataInterface{    /**     * @var ConfigBasedIntegrationManager     */    private $integrationManager;    /**     * @param ConfigBasedIntegrationManager $integrationManager     */    public function __construct(ConfigBasedIntegrationManager $integrationManager)    {        $this->integrationManager = $integrationManager;    }    /**     * {@inheritdoc}     */    public function install(ModuleDataSetupInterface $setup, ModuleContextInterface $context)    {        $this->integrationManager->processIntegrationConfig(['testIntegration2']);    }}

The InstallData script above will read data from some "#adding_xml_settings">XML configuration files then adding the integration into Magento.

"adding_xml_settings">Adding Integration xml setting  files

Magento provides the Integration module, which simplifies the process of defining your integration. This module automatically performs functions such as:

• Managing the third-party account that connects to Magento.
• Maintaining OAuth authorizations and user data.
• Managing security tokens and requests.

There are 2 files those Magento_Integration module can read for processing Integration settings programmatically.

• etc/integration/api.xml for "#define_resource">Define the required resources and;
• etc/integration/config.xml for "#define_integration">Defining an Integration

"define_resource">Define the required resources

The etc/integration/api.xml file defines which "https://glossary.magento.com/api">API resources the integration has access to.

To determine which resources an integration needs access to, review the permissions defined in each modules etc/acl.xml file.

In the following example, the test integration requires access to the following resources in the Sales & Catalog modules:

"testIntegration2">                                "Magento_Customer::customer" ?-->