Portals are the pieces of code to connect your HEPTAconnect instance to other APIs for data transfer. They are most likely installed via composer or as a plugin in your integration (e.g. Shopware 6).
How to get a portal?
There are multiple sources for portals. Some of them are available as open source on GitHub and packagist like our Shopware 6 portal. There are many client specific implementations for known and custom APIs we (HEPTACOM GmbH) and our HEPTAconnect partners developed in the past. To get information on our previous work and our solutions for your connector project contact us by emailing us to firstname.lastname@example.org.
Develop your own
When you want to develop your portal you can move over from this integrator section over to the portal developer section. There you can find an extensive explanation of all the tools at hand that you need.
When you got access to your portal of choice you can now use composer to install it in your integration. To check whether it got recognized correctly you can check
heptaconnect:portal:list to list all your installed portals. Following by that you can create portal nodes from this portal and assign a rememberable name with the command
heptaconnect:portal-node:add $FQCN nice_alias. Learn more about administering portal nodes in the administrator section.
There are good reasons to alter the behaviour of an existing portal. For this task you use portal extensions. They allow you to completely change the behaviour of any portal and can be mixed with other portal extensions as well. Learn more about decorated flow components like explorers, emitters and receivers in the portal developer section. Learn more about the reasons why and when it is useful to create portal extensions for data tuning.