Mercedes.VehicleManagement.API

UpdateVehicleRequest

Vehicle

The following routes are available for this service:
POST	/v1/{VehicleType}/Vehicle/UpdateVin	Refresh vehicle data
POST	/v1/{VehicleType}/Vehicle/UpdateVehicle	Refresh vehicle data

# frozen_string_literal: true
# encoding: utf-8


require 'json'
require 'servicestack'


class UpdateVinResponse
    include ServiceStack::DTO

    # @return [TrueClass]
    attr_accessor :success
    # @return [Object]
    attr_accessor :data

    def self.properties
        {
            success: { name: 'success' },
            data: { name: 'data' },
        }
    end

end

class UpdateVehicleRequest
    include ServiceStack::DTO

    # @return [String]
    attr_accessor :vehicle_identifier
    # @return [String]
    attr_accessor :vin
    # @return [String]
    attr_accessor :vehicle_type

    def self.properties
        {
            vehicle_identifier: { name: 'vehicleIdentifier' },
            vin: { name: 'vin' },
            vehicle_type: { name: 'vehicleType' },
        }
    end

    def response_type() = UpdateVinResponse
    def get_type_name() = 'UpdateVehicleRequest'
end

Ruby UpdateVehicleRequest DTOs

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /v1/{VehicleType}/Vehicle/UpdateVin HTTP/1.1 
Host: uat-api-vehicle-mgt-mb-dhc.rapp-customers.co.uk 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"vehicleIdentifier":"String","vin":"String","vehicleType":"String"}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"success":false,"data":{}}