Changelog

Notable changes to the TEALCA API.

[Unreleased]

GET /store, GET /store/{code} and GET /store/coverage: every store includes the is_platform field.
POST /shipment, GET /shipment/{shipment_identification}, POST /shipment/cancel, GET /customer/{customer_identification}/shipments, POST /preshipment and GET /preshipment/{preshipment_identification}: origin_store and destination_store include the is_platform field.
GET /location: default_destination_store includes the is_platform field.
GET /store/coverage: new optional location_code parameter. When the coordinates do not resolve to a single store of that location, the endpoint returns the platform store that serves it.

GET /location: default_destination_store is resolved with the new coverage algorithm, so it can be a different store, it can be a platform, and it is null when the location has no coverage.
POST /shipment, POST /preshipment, POST /shipment/price-calculation, GET /shipment/{shipment_identification}/price-calculation, POST /warehouse/delivery-order and POST /shipment-bulk/{header_id}/execute: when origin.store or destination.store is omitted for an office service, the store is always resolved by coverage, so the assigned store may differ from the one linked to the location and may be a platform.
On those same endpoints, a store resolved by coverage is also validated against locked stores, so a shipment that reaches a locked store without naming it is now rejected.
On those same endpoints, coverage errors are reported by reason, which includes uncovered areas, inactive stores, locked stores, stores outside the catalog and locations covered by several stores without a platform. The message lists the candidate stores.
POST /shipment, POST /document, POST /manifest and POST /preshipment: the response list keeps the order of the list sent in the request.
GET /store/coverage: a location_code that does not exist is reported with the nonexistent location error, and a point outside coverage is reported as not being within a TEALCA coverage area.

POST /shipment, POST /preshipment, POST /shipment/price-calculation, GET /shipment/{shipment_identification}/price-calculation, POST /warehouse/delivery-order and POST /shipment-bulk/{header_id}/execute: sending origin.coordinates or destination.coordinates for home pickup or home delivery no longer causes a server error.
On those same endpoints, each shipment is priced with the zone that corresponds to it, which prevents a shipment from being priced with another shipment's zone.

POST /shipment, POST /preshipment and POST /document: the name of a natural person must contain at least two words, and the name of a juridic account also accepts the + character.

POST /shipment, POST /preshipment and PUT /shipment/{shipment_header_id}/shipment-parcel: the error message when creating shipments for corporate customers with a volumetric factor of zero or less now indicates the billing account code and the configured factor, instead of being a generic message.
POST /shipment, POST /preshipment and POST /document: the error message for invalid names distinguishes between natural and juridic accounts.

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.