Has this bug been resolved?
Apparently this works using the bulk line items endpoint:
However, as OP said, it does not work for the normal single line item creation endpoint:
You could consider using the bulk line item endpoint to reduce the amount of requests you make to clover end in this case (as long as all your properties are supported by this endpoint)
The atomic order API has the same issue. In our case updating it after creation doesn't work, as we don't know which order item to assign which user data (as the IDs are generated by Clover).
5 People are following this question.