Infigo Iframe Integration Overview and Setup
The Infigo iframe integration allows you to embed the Infigo Design Tool (Editor) directly into your application, enabling customers to design products seamlessly within your platform. This integration provides a comprehensive solution by offering the entire Infigo workflow, from creating output/artworks to pushing data into MIS systems and supporting approval processes.
Resources and Key Links
Demo Application
GitHub Source Code: iframe-demo-app
Description: This application demonstrates a real iframe integration of the Infigo Design Tool (Editor) for investigation and debugging purposes. It is recommended to use this demo as a reference, and for production implementations, manage all API interactions via backend calls to maintain security.
Infigo Documentation API
Description: Comprehensive documentation covering all available endpoints utilized by the demo application. This API provides the necessary endpoints to enable the full Infigo workflow, including creating product outputs, interfacing with MIS systems, and integrating approval functionalities.
Iframe Integration Documentation
Description: Detailed documentation on iframe configuration, available settings, and customizations. This wiki serves as a guide for setting up and troubleshooting iframe integration, allowing you to customize the Infigo Editor to fit seamlessly within your application.
Important Information
To navigate the Safari (and potentially other browsers in the future) third-party cookie security policy, it's crucial to set up a subdomain binding and SSL certificate on your Infigo storefront. This subdomain must match the domain of the requesting site. Failure to configure this beforehand will lead to integration issues.
When embedding our editor in your third-party software, since we use an iframe approach, it’s essential that the domain of the Infigo website hosting your editor and products matches your third-party site domain.
Example:
Your software domain – www.mywebsite.com
Infigo editor domain – personalise.mywebsite.com
Additional Notes:
API Security: To protect sensitive data, all API calls should be managed on the server side. Avoid making API requests directly from the client side to prevent exposing the API endpoints and authentication tokens.
Integration Flow: Use the demo application and documentation as a reference to develop a secure backend handling mechanism for iframe-related API calls in production environments. With this setup, your application can provide customers a powerful design tool and seamless access to the complete Infigo workflow.