The Bold platform connector is designed to be flexible, and you can implement it with a variety of platform configurations. The following sections include examples of the different configurations.
The following diagrams depict only examples of platform connector architectures. They are not intended to be comprehensive or complete. Many other implementations are possible.
Connecting a traditional platform
If Bold does not provide out-of-the-box support for the platform you want to use, the Bold platform connector can serve as a bridge between the existing platform and the Bold APIs.
In this scenario, the store does not have the ability to modify the platform code and can only interact with the platform via webhooks.
This platform connector implementation needs to be aware of multiple stores. When receiving a request from Bold, the platform connector must use an identifier in the request to determine which set of credentials to use for authenticating that request and subsequent requests to the platform.
Connecting an open source platform
Some platforms are considered open source, such as Magento. In this case, the platform connector code is duplicated across different instances of the platform, each running on different servers. No store lookup or additional processes for verification are required to use this implementation. Variables used for authentication could be defined as environment variables on each instance.
Connecting a custom platform
The platform connector also enables stores that have custom platforms to use Bold. In this scenario, the platform connector only needs to be aware of the one store, and the store has the ability to modify the platform's code. No store lookup or additional processes for verification are required to use this implementation. Variables used for authentication could be defined as environment variables on the store.
Implementations for a platform connector with a custom platform vary widely based on store needs. The following diagrams show some examples.