Extended historic integration

This guide describes the overview of the integration with the Order API, and the usage of the Webhook API integration to upload to Wapping all the historic operations of the customers, once they are validated in the platform.

This integration applies when the ingestion of the full detail of orders is required by the business, in 90% of the cases the standard direct migration is preferred.

The process is as follows:

1. Integration with Webhook API to receive triggers when new customers are created.
2. Integration with Order API to upload the historic orders
3. Trigger the upload of the orders associated to the customer when the webhook is received.

*A variation on the step 3 can be done, in wich the process is not synchronous and instead a daily update of the orders of the created customers that day is sent. Any approach is valid.

The important bit is that the tickets uploaded are always associated with a customer, and for this to be done, a customer has to be created and validated first in the platform, so no preload of tickets or customers are done, and instead the progressive organic validation of the customers in the new platform (even if they were previous customers of the business) is what drives the historic syncronization.