Changelog

Notable changes to the TEALCA API.

[Unreleased]

GET /tracking/shipment/{shipment_identifier_list}: each shipment in the response includes the preshipment_number and shipment_partner_id fields, empty when the shipment has none.
POST /shipment, POST /preshipment, and POST /warehouse/delivery-order: the shipment_list, preshipment_list, and delivery_order_list fields accept at most 20 items per request.

POST /shipment: the shipper.name and consignee.name fields accept the characters ñ and Ñ.

All endpoints are also available under the /api/v1/ prefix.
New endpoint GET /customer/{customer_identification}/shipments: lists the shipments where the customer is the shipper or the consignee, with cursor-based pagination.

Registering a POD (proof of delivery) through POST /pod also updates the shipment's status and tracking information.
POST /pod: the account_id field accepts a UUID in any standard format. Malformed values are rejected during request validation instead of causing a server error.
POST /shipment: creation of corporate shipments is rejected when the destination store (destination.store) is not available, or is blocked, for the billing account's agreement. The error message identifies the shipment, the store, and the reason.

Routes without the /api/v1/ prefix will be removed soon. Switching to the versioned routes is recommended.

PUT /shipment/{shipment_header_id}/shipment-parcel: the path parameter accepts either the shipment ID or the shipment number.
POST /shipment: shipment_header_reference values used by canceled or replaced shipments can be reused on new shipments.

New endpoint GET /preshipment: returns the preshipments created between date_from and date_to, each with its shipper, consignee, current status, the date each stage was reached, and the declared, validated, and charged weights. Results are paginated with cursor and page_size. The maximum range per query is 31 days.
New /shipment-bulk endpoints for the new bulk shipment upload process in MiTealca: POST /shipment-bulk, GET /shipment-bulk/list, GET /shipment-bulk/{header_id}, GET /shipment-bulk/{header_id}/progress, and GET /shipment-bulk/{header_id}/file.

GET /tracking/shipment/{shipment_identifier_list}: each tracking record includes the event_id field, along with event and event_category, so consuming systems can react without depending on the text.

Bug fixes in price calculation (POST /shipment/price-calculation and GET /shipment/{shipment_identification}/price-calculation), shipment creation (POST /shipment), and the public documentation at /api/docs.