openapi: 3.0.0
x-zally-ignore:
  - 224
  - 176 # Ignored since it is returning the errors as XML
  - 151 # Ignored since it is returning the errors as XML
  - 118 # Ignored to keep it consistent with the VDA XML naming convention
  - 105 # The scopes being used to segregate profiles do not match the expected Zalando regex
info:
  x-audience: external-partner
  x-api-id: fabb3f14-4c29-4ca6-812f-0a84b79a8dbe
  title: VDA Finished Vehicles Transport Order Partner API
  description: |
    This API can be used by external partner applications (service providers) to exchange VDA Finished Vehicle
    Logistics (FVL) messages with the vehicle manufacturer (ordering party).
    
    The VDA Finished Vehicle Logistics (FVL) standard specifies an electronic message for automated data exchange
    between vehicle manufacturers and providers of logistic services. It is an industry-wide initiative in Europe
    led by the Association of European Vehicle Logistics (ECG), Odette International and
    the Verband der Automobilindustrie (VDA).

    ## Typical Use Cases
    * retrieve Transport orders (FV14a) for transport service providers from the ordering party
    * provide Transport order responses (FV14b) to the ordering party from a transport service provider
    * provide Transport status report (FV17) to the ordering party from a transport service provider
    * retrieve Service orders (FV18) for transport service providers from the ordering party
    * provide Service order responses (FV18) to the ordering party from a transport service provider
    * retrieve Compound Transport orders (FV14a) for compound service providers from the ordering party
    * retrieve Transport capacity reservations (FV25a) from the ordering party
    * provide Transport capacity reservations responses (FV25b) to the ordering party from a transport service provider

    ## Available URLs:
    * https://api.finished-vehicles.outbound-order-book.rio.cloud
    * https://test.api.finished-vehicles.outbound-order-book.rio.cloud
    
    The first URL is the production API that should be used for real, live data. The second URL is a test API used for
    testing purposes. Both APIs provide the same endpoints, but the test API is not meant for live data.
    Both APIs require proper authentication as specified in the original OpenAPI document.

    ## Test API Usage
    
    To use the test API, replace the base URL of your requests with the test API base URL. For instance, if you were
    previously making a GET request to https://api.finished-vehicles.outbound-order-book.rio.cloud/transport-orders,
    now make that same GET request to https://test.api.finished-vehicles.outbound-order-book.rio.cloud/transport-orders
    for testing. The test API provides you with a new set of data each day. 
    
    ### Test Data Retention Policy:
    Data on the test API will be stored for a specified number of days for testing purposes, after which it will be
    automatically deleted. Please do not use the test API for storing important or long-term data.
    
    ## API Guidelines
    * There are rate limits in place to prevent excessive incoming requests. Be aware of this when implementing against the API.
    * When polling the GET endpoints, a sensible polling interval should be used to stay within rate limits. 
      We recommend an interval of 10 minutes.
    * When polling the GET endpoints, a "Next" link is part of the response and should be used in the next request to 
      only retrieve newer orders. The link includes an after parameter that serves as an offset to pull the next orders.
    * When polling the GET endpoints, a sensible limit should be used. We suggest a limit of 100 which is the default 
      when no limit parameter is set.
    * Only send updates when new or updated information is present in the payload.
    * When the response contains a 4xx status code, process the returned error message before retrying the request. 
      The error message will indicate how to solve the underlying issue.
    
    Please note that failure to adhere to the guidelines may result in the suspension of your API access.

  version: "0.0.1"
  contact:
    name: rio-team-outbound
    email: outbound.order.book@rio.cloud
    url: https://rio.cloud
servers:
  - url: 'https://api.finished-vehicles.outbound-order-book.rio.cloud'
    description: This server URL is used exclusively to exchange productive data generated by the ordering party.
  - url: 'https://test.api.finished-vehicles.outbound-order-book.rio.cloud'
    description: This server URL is used exclusively to exchange data generated for test purposes by Outbound order book.
paths:
  '/transport-orders':
    get:
      description: |
        A Feed/Stream API that allows consuming all new or updated transport orders, in chronological order similar to a queue.        

        It is possible to navigate through the transport orders via the provided `Next` link in the response.
        By using the link, the next batch of transport orders can be retrieved, see ResourceListLinks for more
        details.

        ## Examples

          Fetch an initial limited list of 100 transport orders
          ```
          GET /transport-orders?limit=100
          ```

          Fetch the next limited list of 100 transport orders that occurred after the previous fetched list,
          based on the `Next` link. Here the `after` parameter indicates the cursor used for pagination, which encodes
          the page position to safely recreate the request result.
          ```
          GET /transport-orders?limit=100&after=f8d0466b-f509-49c5-8ddf-d5793fae7ec0
          ```
      parameters:
        - $ref: '#/components/parameters/after'
        - $ref: '#/components/parameters/limit'
      responses:
        '200':
          description: Ok
          content:
            application/xml:
              schema:
                $ref: '#/components/schemas/TransportOrders'
        default:
          content:
            application/problem+xml:
              schema:
                $ref: 'https://opensource.zalando.com/problem/schema.yaml#/Problem'
          description: An error occurred. See status code and problem object for more information.
      security:
        - oauth2:
            - finished-vehicle.transport-order.read
            - logistics.service-provider
      tags:
        - TransportOrder

  '/transport-order-responses/{document-id}':
    parameters:
      - $ref: '#/components/parameters/documentId'
    put:
      description: |
        Create or update a transport order response for one or several transport orders.

        ## Typical use cases

          * Confirm a new vehicle transport order
          * Update an existing vehicle transport order response

        ## Example

          PUT a new transport order response to the Outbound Order Book
          ```
          PUT /transport-order-responses/1234abc567
          ```
      requestBody:
        description: The Transport order responses to be created or updated.
        required: true
        content:
          application/xml:
            schema:
              $ref: '#/components/schemas/TransportOrderResponseEnvelope'
      responses:
        '201':
          description: Created
        default:
          content:
            application/problem+xml:
              schema:
                $ref: 'https://opensource.zalando.com/problem/schema.yaml#/Problem'
          description: An error occurred. See status code and problem object for more information.
      security:
        - oauth2:
            - finished-vehicle.transport-order-response.write
            - logistics.service-provider
      tags:
        - TransportOrderResponse

  '/transport-status-reports/{document-id}':
    parameters:
      - $ref: '#/components/parameters/documentId'
    put:
      description: |
        Transport status report messages (FV17) are exchanged between service providers and the ordering party at various
        stages in the distribution process (e.g. when a vehicle belonging to a transport order was loaded or unloaded).

        The reports are used to keep the ordering party up to date about the execution of a transport order. A reference
        to a transport order document ID and its vehicle is required.

        You can create a transport status report for one or several transport orders and vehicles.

        The endpoint is used by Logistics service providers (LSP) performing transports of vehicles

        ## Supported use cases

          * Report the loading of a vehicle onto a means of transport (Status Code 48)
          * Report the unloading of a vehicle from a means of transport (Status Code 346)

        ## Example

          PUT a new transport status report to the Outbound Order Book
          ```
          PUT /transport-status-reports/1234abc567
          ```
      requestBody:
        description: The Transport status report to be created.
        required: true
        content:
          application/xml:
            schema:
              $ref: '#/components/schemas/TransportStatusReportEnvelope'
      responses:
        '201':
          description: Created
        default:
          content:
            application/problem+xml:
              schema:
                $ref: 'https://opensource.zalando.com/problem/schema.yaml#/Problem'
          description: An error occurred. See status code and problem object for more information.
      security:
        - oauth2:
            - finished-vehicle.transport-order-status.write
            - logistics.service-provider
      tags:
        - TransportStatusReport

  '/service-orders':
    get:
      description: |
        A Feed/Stream API that allows consuming all new or updated service orders, in chronological order similar to a queue.

        It is possible to navigate through the service orders via the provided `Next` link in the response.
        By using the link, the next batch of service orders can be retrieved, see `ResourceListLinks` for more
        details.

        ## Examples

          Fetch an initial limited list of 100 service orders
          ```
          GET /service-orders?limit=100
          ```

          Fetch a batch of 100 service orders that occurred after the previously fetched list.
          Here the `after` parameter indicates the cursor used for pagination.
          ```
          GET /service-orders?limit=100&after=f8d0466b-f509-49c5-8ddf-d5793fae7ec0
          ```
      parameters:
        - $ref: '#/components/parameters/after'
        - $ref: '#/components/parameters/limit'
      responses:
        '200':
          description: Ok
          content:
            application/xml:
              schema:
                $ref: '#/components/schemas/ServiceOrders'
        default:
          description: An error occurred. See status code and problem object for more information.
          content:
            application/problem+xml:
              schema:
                $ref: 'https://opensource.zalando.com/problem/schema.yaml#/Problem'
      security:
        - oauth2:
            - finished-vehicle.service-order.read
            - logistics.service-provider
      tags:
        - ServiceOrder

  '/service-order-responses/{document-id}':
    parameters:
      - $ref: '#/components/parameters/documentId'
    put:
      description: |
        Create or update a service order response.

        ## Typical use cases

          * Complete a vehicle service order
          * Update a existing completion of a vehicle service order

        ## Example

          PUT a new service order response to the Outbound Order Book
          ```
          PUT /service-order-responses/5hBnp33Z
          ```
      requestBody:
        description: The Service order response to be created or updated.
        required: true
        content:
          application/xml:
            schema:
              $ref: '#/components/schemas/ServiceOrderEnvelope'
      responses:
        '204':
          description: No Content
        default:
          content:
            application/problem+xml:
              schema:
                $ref: 'https://opensource.zalando.com/problem/schema.yaml#/Problem'
          description: An error occurred. See status code and problem object for more information.
      security:
        - oauth2:
            - finished-vehicle.service-order.write
            - logistics.service-provider
      tags:
        - ServiceOrder

  '/compound-transport-orders':
    get:
      description: |
        A Feed/Stream API that allows consuming all new or updated compound transport orders in chronological order similar to a queue.

        It is possible to navigate through the compound transport orders via the provided `Next` link in the response.
        By using the link, the next batch of orders can be retrieved, see ResourceListLinks for more
        details.

        ## Examples

          Fetch an initial limited list of 100 order
          ```
          GET /compound-transport-orders?limit=100
          ```

          Fetch the next limited list of 100 compound transport orders that are available after the previously fetched list,
          based on the `Next` link. Here the `after` parameter indicates the cursor used for pagination, which encodes
          the page position to safely recreate the request result.
          ```
          GET /compound-transport-orders?limit=100&after=f8d0466b-f509-49c5-8ddf-d5793fae7ec0
          ```
      parameters:
        - $ref: '#/components/parameters/after'
        - $ref: '#/components/parameters/limit'
      responses:
        '200':
          description: Ok
          content:
            application/xml:
              schema:
                $ref: '#/components/schemas/CompoundTransportOrders'
        default:
          content:
            application/problem+xml:
              schema:
                $ref: 'https://opensource.zalando.com/problem/schema.yaml#/Problem'
          description: An error occurred. See status code and problem object for more information.
      security:
        - oauth2:
            - finished-vehicle.compound-transport-order.read
            - logistics.service-provider
      tags:
        - CompoundTransportOrder

  '/compound-status-reports/{document-id}':
    parameters:
      - $ref: '#/components/parameters/documentId'
    put:
      description: |
        The Outbound Order Book distinguishes between transport status messages concerning the transport and those concerning the compound.
        The latter is called Compound status reports in our context, despite both using the VDA FV 17 transport status report message.
        
        Compound status report messages (FV17) for compounds are exchanged between compound service provider (CSP) and the ordering party
        at various stages in the distribution process (e.g. when a vehicle arrives or departs from a compound).

        The reports are used to keep the oderding party up-to-date about the arrival or departure of vehicles from
        a compound. For both types of reports a reference to a compound transport order document ID and its vehicle is required.

        You can create a compound status report for one or several compound transport orders and vehicles.

        The endpoint is used by CPSs storing vehicles for some time.

        ## Supported use cases

          * Report the completed arrival of a vehicle at a compound (Status Code 1)
          * Report the completed departure of a vehicle from a compound (Status Code 24)

        ### This implementation adds the following restriction on top of the FV17 standard, to facilitate the process and prevent possible ambiguities of intent.
        
        * It is not allowed to mix different status codes within a single FV17 message. You need to send a FV17 message containing only arrival completed status codes and a second FV17 containing only departure completed status codes.
        * For `TransportMeansType` TRUCK and TRAIN the `VehicleTransportStatusReport/TransportStatus/TransportMeansID` is required
        * The `VehicleTransportStatusReport/ShipmentStatus`must contain at least one status
        * The `VehicleTransportStatusReport/ShipmentStatus`must contain must contain VehicleID with @Qualifier = VIN
        * A location ID must be present for each vehicle in the status update. (`ShipmentStatus/Status/Location`)
        * At least one reference with qualifier `TransportOrder` in `VehicleTransportStatusReport/Header/Reference` must be given
        * The supplied `VehicleTransportStatusReport/TransportStatus/StatusDetails/StatusCode` needs to match the `VehicleTransportStatusReport/ShipmentStatus/Status/StatusCode`
        * Only up to 5000 vehicles can be added to the same load. The load can be given a free identifier via the `VehicleTransportStatusReport/Header/Reference` with qualifier `LoadingList`. The load ID must be unique for the CSP.
        * For now it is not possible to update the departure completed or arrival completed status.
        
        ### When submitting a departure completed without a transport order ("unannounced departure"), the following rules apply.
        
        * You may use dummy reference `WITHOUTTRANSPORTORDER` with qualifier `TransportOrder` in `VehicleTransportStatusReport/Header/Reference`, since a reference is mandatory.
        * The fields `VehicleTransportStatusReport/ShipmentStatus/Status`, `VehicleTransportStatusReport/ShipmentStatus/Status/LocationID` and `VehicleTransportStatusReport/TransportStatus/TransportMeansType` must be present.
        * The only supported `MeansOfTransportType` for unannounced departures are `RORO_VESSEL`, `CONTAINER_VESSEL` and `OWN_WHEELS`.
        * It is not possible to send status updates for vehicles with transport order and without transport order in the same message.
        * It is not possible to update the departure completed status.
        
        ## Example

          PUT a new compound status report to the Outbound Order Book
          ```
          PUT /compound-status-reports/1234abc567
          ```
      requestBody:
        description: The compound status report to be created.
        required: true
        content:
          application/xml:
            schema:
              $ref: '#/components/schemas/TransportStatusReportEnvelope'
      responses:
        '201':
          description: Created
        default:
          content:
            application/problem+xml:
              schema:
                $ref: 'https://opensource.zalando.com/problem/schema.yaml#/Problem'
          description: An error occurred. See status code and problem object for more information.
      security:
        - oauth2:
            - finished-vehicle.compound-transport-order-status.write
            - logistics.service-provider
      tags:
        - CompoundStatusReport

  '/transport-capacity-reservations':
    get:
      description: |
        A Feed/Stream API that allows consuming all new or updated transport capacity reservations in chronological order similar to a queue.

        It is possible to navigate through the transport capacity reservations via the provided `Next` link in the response.
        By using the link, the next batch of transport capacity reservations can be retrieved, see ResourceListLinks for more
        details.

        ## Examples

          Fetch an initial limited list of 100 transport capacity reservations
          ```
          GET /transport-capacity-reservations?limit=100
          ```

          Fetch the next limited list of 100 transport capacity reservations that occurred after the previous fetched list,
          based on the `Next` link. Here the `after` parameter indicates the cursor used for pagination, which encodes
          the page position to safely recreate the request result.
          ```
          GET /transport-capacity-reservations?limit=100&after=f8d0466b-f509-49c5-8ddf-d5793fae7ec0
          ```
      parameters:
        - $ref: '#/components/parameters/after'
        - $ref: '#/components/parameters/limit'
      responses:
        '200':
          description: Ok
          content:
            application/xml:
              schema:
                $ref: '#/components/schemas/TransportCapacityReservations'
        default:
          content:
            application/problem+xml:
              schema:
                $ref: 'https://opensource.zalando.com/problem/schema.yaml#/Problem'
          description: An error occurred. See status code and problem object for more information.
      security:
        - oauth2:
            - finished-vehicle.transport-order.read
            - logistics.service-provider
      tags:
        - TransportCapacityReservation

  '/transport-capacity-reservation-responses/{document-id}':
    parameters:
      - $ref: '#/components/parameters/documentId'
    put:
      description: |
        Create or update a transport capacity reservation response for one capacity reservation.

        ## Typical use cases

          * Confirm a new transport capacity reservation
          * Update an existing transport capacity reservation

        ## Example

          PUT a new transport capacity reservation response to the Outbound Order Book
          ```
          PUT /transport-capacity-reservation-response/1234abc567
          ```
      requestBody:
        description: The transport capacity reservation response to be created or updated.
        required: true
        content:
          application/xml:
            schema:
              $ref: '#/components/schemas/TransportCapacityReservationResponseEnvelope'
      responses:
        '201':
          description: Created
        default:
          content:
            application/problem+xml:
              schema:
                $ref: 'https://opensource.zalando.com/problem/schema.yaml#/Problem'
          description: An error occurred. See status code and problem object for more information.
      security:
        - oauth2:
            - finished-vehicle.transport-order-response.write
            - logistics.service-provider
      tags:
        - TransportCapacityReservationResponse

components:
  schemas:
    TransportOrders:
      description: |
        A list of transport orders with information where to retrieve the next batch
      type: object
      required:
        - Items
        - _Links
      properties:
        Items:
          type: array
          xml:
            wrapped: true
          items:
            $ref: '#/components/schemas/TransportOrderEnvelope'
        _Links:
          $ref: '#/components/schemas/ResourceListLinks'

    TransportOrderEnvelope:
      description: |
        It represents the industry standard XML of a VDA Finished Vehicle Logistics message for vehicle
        transport orders (FV14a). The XML schema specification can be found in the referenced external documents.
      externalDocs:
        description: |
          VDA Finished Vehicle Logistics XSD schema file for a Vehicle Transport Order (FV14a).
        url: https://www.odette.org/resources/fvl-vehicle-transport-order-2
      type: string
      xml:
        name: Envelope
        namespace: 'https://api-doc.finished-vehicles.outbound-order-book.rio.cloud/VW/xsd/v_1.2/FV14_VehicleTransportOrder.xsd'

    TransportOrderResponseEnvelope:
      description: |
        This field contains a XML representing the VDA Finished Vehicle Logistics standard for vehicle transport order
        responses (FV14b). The XML schema specification can be found in the referenced external documents.
      externalDocs:
        description: |
          VDA Finished Vehicle Logistics XSD schema file for a Vehicle Transport Order Response Message (FV14b).
        url: https://www.odette.org/resources/fvl-vehicle-transport-order-response-2
      type: string
      xml:
        name: Envelope
        namespace: 'https://api-doc.finished-vehicles.outbound-order-book.rio.cloud/VW/xsd/v_1.2/FV14_VehicleTransportOrderResponse.xsd'

    TransportCapacityReservations:
      description:
        A list of transport capacity reservations with information where to retrieve the next batch.
      type: object
      required:
        - Items
        - _Links
      properties:
        Items:
          type: array
          xml:
            wrapped: true
          items:
            $ref: '#/components/schemas/TransportCapacityReservationEnvelope'
        _Links:
          $ref: '#/components/schemas/ResourceListLinks'

    TransportCapacityReservationEnvelope:
      description: |
        It represents the industry standard XML of a VDA Vehicle Transport Capacity Reservation Message
        (FV25a). The XML schema specification can be found in the referenced external documents.
      externalDocs:
        description: |
          VDA Finished Vehicle Logistics XSD schema file for a Vehicle Transport Capacity Reservation Message (FV25a).
        url: https://www.odette.org/resources/fvl-vehicle-status-request-3
      type: string
      xml:
        name: Envelope
        namespace: 'https://api-doc.finished-vehicles.outbound-order-book.rio.cloud/VW/xsd/v_1.2/FV25_VehicleTransportCapacityReservation.xsd'

    TransportCapacityReservationResponseEnvelope:
      description: |
        This field contains a XML representing the VDA Finished Vehicle Logistics standard for vehicle transport capacity reservation
        responses (FV25b). The XML schema specification can be found in the referenced external documents.
      externalDocs:
        description: |
          VDA Finished Vehicle Logistics XSD schema file for a Vehicle Transport Capacity Response Message (FV25b).
        url: https://www.odette.org/resources/fvl-vehicle-status-request-3-2
      type: string
      xml:
        name: Envelope
        namespace: 'https://api-doc.finished-vehicles.outbound-order-book.rio.cloud/VW/xsd/v_1.2/FV25_VehicleTransportCapacityReservationResponse.xsd'

    TransportStatusReportEnvelope:
      description: |
        This field contains a XML representing the VDA Finished Vehicle Logistics standard for vehicle transport status
        reports (FV17). The XML schema specification can be found in the referenced external documents.
      externalDocs:
        description: |
          VDA Finished Vehicle Logistics XSD schema file for a Vehicle Transport Status Report Message (FV17).
        url: https://www.odette.org/resources/fvl-vehicle-transport-status-report-3
      type: string
      xml:
        name: Envelope
        namespace: 'https://api-doc.finished-vehicles.outbound-order-book.rio.cloud/VW/xsd/v_1.2/FV17_VehicleTransportStatusReport.xsd'

    ServiceOrders:
      description:
        A list of the service orders. Also containing information from where to retrieve the next batch.
      type: object
      required:
        - Items
        - _Links
      properties:
        Items:
          type: array
          xml:
            wrapped: true
          items:
            $ref: '#/components/schemas/ServiceOrderEnvelope'
        _Links:
          $ref: '#/components/schemas/ResourceListLinks'

    ServiceOrderEnvelope:
      description: |
        It represents the industry standard XML of a VDA Finished Vehicle Logistics message for Service Orders (FV18).
        The Envelope can be of subtype Vehicle Service Order or Vehicle Service Order Response, which should match to
        the used endpoint.
        The XML schema specification can be found in the referenced external documents.
      externalDocs:
        description: |
          VDA Finished Vehicle Logistics XSD schema file for a Vehicle Transport Order (FV18).
        url: https://www.odette.org/resources/fvl-vehicle-service-order-2
      type: string
      xml:
        name: Envelope
        namespace: 'https://api-doc.finished-vehicles.outbound-order-book.rio.cloud/VW/xsd/v_1.2/FV18_VehicleServiceOrder.xsd'

    CompoundTransportOrders:
      description: |
        A list of compound transport orders with information where to retrieve the next batch
      type: object
      required:
        - Items
        - _Links
      properties:
        Items:
          type: array
          xml:
            wrapped: true
          items:
            $ref: '#/components/schemas/TransportOrderEnvelope'
        _Links:
          $ref: '#/components/schemas/ResourceListLinks'

    ResourceListLinks:
      type: object
      required:
        - Self
        - Next
      description: |
        All links are (absolute) URLs.

         * The `Self` link is for the current resource list.
         * The `Next` link is always present and will return the next batch of resources, or will return an empty list
           of items if there are no more resources at this time. Being a cursor used for pagination, which encodes the
           page position to safely recreate the request result.

        Use the `Next` link for future requests to retrieve the next batch of events.
      properties:
        Self:
          $ref: "#/components/schemas/Link"
        Next:
          $ref: "#/components/schemas/Link"
      readOnly: true
    Link:
      type: object
      required:
        - Href
      properties:
        Href:
          type: string
          example: "https://..."
      readOnly: true

  parameters:
    documentId:
      description: |
        Order document-id generated by the user of API.
        It needs to match the document-id provided in the payload body.
      name: document-id
      in: path
      required: true
      schema:
        type: string
        minLength: 1
        maxLength: 35
      example: 5hBn-p33Z
    after:
      in: query
      name: after
      required: false
      description: |
        Return all events which occurred after the specified cursor, which encodes the
        page position to safely recreate the request result.
        Can be omitted to read all existing events available at the Outbound Order Book.
      schema:
        type: string
    limit:
      in: query
      name: limit
      required: false
      description: Specifies a number of response items to retrieve in the response. A value between 10 and 1000 is allowed.
        If the parameter is not specified it will default to 100.
      schema:
        type: integer
        default: 100
        minimum: 10
        maximum: 1000

  securitySchemes:
    oauth2:
      type: oauth2
      flows:
        clientCredentials:
          scopes:
            finished-vehicle.transport-order-response.write: Write access for transport order responses in the VDA finished vehicles transport order connector. Can only be used here in combination with the scope for service providers.
            finished-vehicle.transport-order-status.write: Write access for transport order statuses in the VDA finished vehicles transport order connector. Can only be used here in combination with the scope for service providers.
            finished-vehicle.transport-order.read: Read access for transport orders in the VDA finished vehicles transport order connector. Can only be used here in combination with the scope for service providers.
            finished-vehicle.service-order.write: Write access for service orders in the VDA finished vehicles connector. Can only be used here in combination with the scope for service providers.
            finished-vehicle.service-order.read: Read access for service orders in the VDA finished vehicles connector. Can only be used here in combination with the scope for service providers.
            finished-vehicle.compound-transport-order.read: Read access for compound transport orders in the VDA finished vehicles connector. Can only be used here in combination with the scope for service providers.
            finished-vehicle.compound-transport-order-status.write: Write access for compound transport order statuses in the VDA finished vehicles connector. Can only be used here in combination with the scope for service providers.
            logistics.service-provider: Scope used for service provider clients.
          tokenUrl: 'https://auth.iam.rio.cloud/oauth/token'
