open-logistics 0.3.0

Rust client for the Open Logistics Shiprocket and Delhivery APIs.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34

/*
 * Open Logistics — Delhivery
 *
 * OpenAPI description of the Delhivery B2C endpoints wrapped by `open-logistics`.  Source of truth for generated Python and Rust clients. Operation IDs and schema field names are intentionally snake_case so every language exposes the same names.  Delhivery overloads `POST /api/p/edit` for update and cancel, and `GET /api/v1/packages/json/` for single, order, and bulk tracking. OpenAPI permits one operation per path + method, so this spec exposes `orders_edit` and `tracking_fetch`; language facades may alias them as `update`, `cancel`, `by_waybill`, `by_order_id`, and `by_waybills`. 
 *
 * The version of the OpenAPI document: 0.3.0
 * 
 * Generated by: https://openapi-generator.tech
 */

use crate::delhivery::models;
use serde::{Deserialize, Serialize};

/// DelhiveryTrackingResponse : Raw `GET /api/v1/packages/json/` response. `ShipmentData` is provider-shaped and is exposed as-is; there is no client-side normalization. 
#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct DelhiveryTrackingResponse {
    /// Fields the schema allows but does not enumerate.
    #[serde(flatten)]
    pub additional_properties: std::collections::HashMap<String, serde_json::Value>,

    #[serde(rename = "ShipmentData", skip_serializing_if = "Option::is_none")]
    pub shipment_data: Option<Vec<std::collections::HashMap<String, serde_json::Value>>>,
}

impl DelhiveryTrackingResponse {
    /// Raw `GET /api/v1/packages/json/` response. `ShipmentData` is provider-shaped and is exposed as-is; there is no client-side normalization. 
    pub fn new() -> DelhiveryTrackingResponse {
        DelhiveryTrackingResponse {
            shipment_data: None,
            additional_properties: Default::default(),
        }
    }
}