osdm-sys 0.1.0-alpha.3

Specifications for the OSDM API standard. The OSDM specification supports two modes of operation: Retailer Mode and Distributor Mode. The API works identically in both modes, except that in distributor mode the API also returns fare information. The following resources are key to get started: - [Processes](https://osdm.io/spec/processes/) - [Models](https://osdm.io/spec/models/) - [Getting started](https://osdm.io/spec/getting-started/)
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

# BookingPatchRequest

## Properties

Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**external_ref** | Option<**String**> | The unique booking reference in the distributor/retailer system. Usually refers to an order number or PNR. | [optional]
**place_selections** | Option<[**Vec<models::PlaceSelection>**](PlaceSelection.md)> |  | [optional]
**requested_fulfillment_type** | Option<**String**> | Values from the [Fulfillment Type Code List](https://osdm.io/spec/catalog-of-code-lists/#FulfillmentType) Listed values here are examples.  | [optional]
**preferred_fulfillment_media** | Option<**String**> | Fulfillment types. RCT2, RCCST and UIC_PDF are official UIC standards. Notice:`ALLOCATOR_APP` is deprecated and should not be used anymore. The `ALLOCATOR_APP` type is replaced by the `RETAILER_APP` type. `DISTRIBUTOR_APP` was introduced to distinguish between the different types of apps that can be used to fulfill a booking. Values from the [Fulfillment Media Type Code List](https://osdm.io/spec/catalog-of-code-lists/#FulfillmentMediaType) Listed values here are examples.  | [optional]
**used_payment_methods** | Option<[**Vec<models::PaymentMethod>**](PaymentMethod.md)> |  | [optional]

[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)