Hey,
I'm currently developing a solution for editing and adding new contact list entries - editing existing rows is going smoothly, but when adding new ones, the API doesn't seem to recognize the unique identifier column. As an example, when importing rows from a CSV while creating a list with a unique identifier column selected, the inin-outbound-id field in the list becomes the same as the identifier field; I can search for fields with their unique identifiers and edit them this way.
However, when appending new contacts through the API, the new rows seem to not care about the unique identifier column; the inin-outbound-id becomes a hex value instead, making my search function useless. Is there an option I'm missing with the API that allows new additions to also conform to the same scheme with the unique ID column?
I'm using the POST /api/v2/outbound/contactlists/{contactListId}/contacts endpoint.