Idempotency Protection
1 min
When creating loads in FourKites, using the synchronous option requires storing the FourKites load ID returned in the response from the API. This is because updates to loads are triggered via the PATCH operation using that primary key. The POST operation is not idempotent and will cause duplicates if you do not explicitly use the PATCH operation to update existing loads. Care must be taken not to duplicate loads in the platform by running a POST operation multiple times.
Note: Please consult with your FourKites project team if you'd like to explore asynchronous options to connect to the API which offer idempotency with the POST operation.