Customer Mapping
NOTE: The customer you are using in Infigo must be a REGISTERED user (with the customer role: 'Registered').
The customer GUID is required, and when you are mapping customers from your external system to Infigo, you can choose to map the Infigo customer ID, email address, or customer GUID. The first two are readily available in the UI, and the email address should generally match anyway. However, the customer GUID, which is necessary for subsequent API calls, requires an API request to return it.
Depending on how you intend to implement this integration, you can either:
Ensure that all your customers in your external site have a corresponding customer created in Infigo (this usually works well in a fixed B2B scenario).
Use one 'website' user in your system that is always passed to create the editor and place the orders.
Important: Ensure all jobs from one order are linked to a single customer; otherwise, the Create Order call will fail.
In either case, the customer being used needs to have a mapping entry in Infigo that can be sent with the requests. If you don't store the customer GUID, then the following API call is required:
Endpoint:
The id can be the Infigo customer ID, the customer email address, or the customer GUID.
The response to this request contains a variety of customer data, from which we need to capture the "Guid" (responseJSON.Guid).
If you don't have a customer linkage in your system, you can call the Get Customer SSO Url. This will automatically create a customer in Infigo with the provided GUID if the customer is not found. If the customer already exists in Infigo, this call will simply try to generate a new SSO URL for the customer.