Update Checkout Consignment
Updates an existing consignment. The address, line item IDs, and shipping option ID can be updated using this endpoint.
Use a separate PUT request to update the shipping option IDs if you also want to update the address and line item IDs.
To add new shipping options, complete the following steps:
- Use the Add Consignment to Checkout endpoint to add a new [consignment] to a checkout.
- Assign a shipping option to the new consignment by sending a
PUTrequest to update the consignment’sshipping_option_idwith a returned value fromdata.consignments[N].available_shipping_option[N].idobtained in the Add Consignment to Checkout endpoint.
To update an existing address and line item IDs, assign a new address and line item IDs by sending a PUT request.
To prevent lost updates due to concurrent requests overriding changes made by others, it is recommended to enable optimistic concurrency control by including the version field in the request payload. If the provided version does not match the version on the server, a conflict error will be returned, which the client can handle accordingly.
- Assign a shipping option to the new consignment by sending a
PUTrequest to update the consignment’sshipping_option_idwith a returned value fromdata.consignments[N].available_shipping_option[N].idobtained in Step One.
Authentication
OAuth scopes
Authentication header
Further reading
For example requests and more information about authenticating BigCommerce APIs, see Authentication and Example Requests.
For more about BigCommerce OAuth scopes, see our Guide to API Accounts.
For a list of API status codes, see API Status Codes.
Path parameters
ID of the checkout; the same as the cart ID.
Headers
The MIME type of the response body.
Query parameters
Request
The cart version that you expect to apply the updates. If the provided version doesn’t match the current cart version, you will receive a conflict error. This field is optional; if not provided, optimistic concurrency control will not apply.