API adgang til køretøjsoplysninger

API Documentation

Introduction

The Synsbasen API V1 is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. Our API V1 primary acts as an interface to interact with the information available at The Motor Vehicle Agency (DMR). Our API includes all basic vehicle information eg. vin, registration, status, brand, mileage etc. but also includes more advanced information eg. emission, weight, permits and equipment and much more. Additionally our API includes information from the Danish Road Traffic Authority (Færdelsstyrelsen) regarding vehicle inspections and test centers. The Synsbasen API primarily relies on the XML export of the entire vehicle registry, provided weekly by DMR through their public FTP server. We download and update our data to the most recent export every week. Most information included in the DMR export is available through our API V1. We also combine the vehicle data with additional information about debt, insurance and inspections from other data sources. Feel free to submit suggestions/feature requests to info@synsbasen.dk. We have created a forkable Postman collection. The collection contains examples of our most common requests. We regularly expand the collection with new examples.

NB: Remember to update the collection variables with your own private API key.

Base url

1https://api.synsbasen.dk/v1

Authentication

Synsbasen uses API keys to authenticate requests. An API key is private and must not be shared or used across different applications and domains. You can view and manage your API keys in your dashboard. Required Headers All requests require you to include the following headers: Authorization: Bearer <APIKEY> Content-Type: application/json Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth. Requests without authentication will fail - this also applies to free endpoints. Sign up now and get a free API key.

Authentications

1Authorization: Bearer <APIKEY>
2Content-Type: application/json

Response Codes

Our API uses conventional HTTP response codes to indicate the success or failure of an API request. Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error that failed given the information provided (e.g. a required parameter was omitted, insufficient funds etc.). Codes in the 5xx range indicate an error with Synsbasen’s servers.

HTTP Status Codes

1200OK
2400Bad Request
3401Unauthorized
4403Forbidden
5404Not Found
6429Too Many Requests
7500Internal Server Error

Expand

Some endpoints contains additional information which is not included in the response by default. You can include this information as an expanded response using the expand query parameter on supported endpoints. Expandable resources are noted in this documentation both in the request- and response parameters wherever expanded resourses is available. Example The vehicles endpoint includes 14 expandable resources. You can include the emission data by adding ?expand[]=emission to the request of the vehicles endpoint. You can expand multiple attributes at once by including multiple query parameters eg. ?expand[]=emission&expand[]=weight. See vehicles for the complete list of expandable resources.

Requires: Expand

QUERY STRING

1?expand[]=emission

Response

{
  "data": {
    "id": 1004501200018020,
    "registration": "AS87640",
    "vin": "VF7X1REVF72378327",
    ...,
    "emission": {
      "co2": 100.0,
      "co": 274.9,
      "hc_plus_nox": 0.0,
      "nox": 25.5,
      "particles": null,
      "particle_filter": false,
      "smoke_density": null,
      "smoke_density_engine_speed": 0,
      "energy_class": "A++",
      "euronorm": "Euro V"
    }
  }
}

Search

Some endpoints allows you to include a request body to make advanced searches. The request body object consists of optional parameters regardings filtering, sorting, page index and size etc., which allows you to customize the query to your specific needs. The keys in the query object is called search matchers and consists of the name of the attribute concatenated with a predicate. The predicate determines how to match the attribute with the search value. For instance, using registration_start on the vehicles endpoint will only return vehicles where registration starts with the given search value. Note all predicates are by default case sensitive with the exception of *_i_cont. See available search attributes in the documentation of the individual resources.

Requires: Search

Request parameters

An object where the keys contains of the name of an attribute and a predicate and the values are the term to search for.

A string representing the desired method of the request. If you avoid including a method, the default method is SELECT. The available methods are: - COUNT - SELECT - PERCENTAGE Note: The token cost of a resource is the same regardless of the method used.

A string representing the aggregate function and column to be included in the response. Currently we only support the aggregate function AVG(), but in the future we will support more functions. Example You can calculate the average mileage with the following: select: "AVG(mileage)" NB: You can only specify a single column for now.

A string representing the name of the attribute used to group the results by. group_by is often used with aggregate functions, which you can read more about in the request parameters select and method. Group by supports the following functions: - YEAR(:attribute) - QUARTER(:attribute) - MONTH(:attribute) - WEEK(:attribute) - DAY(:attribute) - ROUND(:attribute) - ROUND(:attribute, :precision) - NEAREST(:attribute, :precision) - SUBSTRING(:attribute, :position, :length) - CONCAT(:attribute, :attribute, ...)

An integer representing the desired page index of the results in the response. The default value is 1.

An integer representing the maximum results in the response. You can set the per page to any integer between 1 and 100. The default value is 10.

A string representing the sorting argument which consists of the name of an attribute and a direction ASC/DESC. You can parse multiple sorting arguments as an array eg. sorts: ["registration ASC", "first_registration_date DESC"].

A string specifying the type of percentage calculation. The default value is RELATIVE. The available types are: RELATIVE: Calculates the percentage based on the sum of each group. This means the values within each group are expressed as a percentage of the group's total. TOTAL: Calculates the percentage based on the total sum of the column. This means the values within each group are expressed as a percentage of the total sum of the column of all groups combined. The percentage type is only used with method: 'PERCENTAGE'.

Response parameters

A hash or array representing the data of the response. The data can be either a hash or an array depending on the method used in the request. If the method is COUNT, the data will be a hash. If the method is SELECT, the data will be an array.

A boolean indicating if there are more pages of results.

An integer representing the current page

An integer representing the total number of pages.

An integer representing the total number of results.

An integer representing the maximum number of results per page.

Predicates

Used to filter results based on an exact match.

Used to filter results based on a value that is not equal.

Used to filter results based on a string starting with a value. This is equivalent to using a LIKE clause in a SQL query with a wildcard suffix.

Used to filter results based on a string ending with a value. This is equivalent to using a LIKE clause in a SQL query with a wildcard prefix.

Used to filter results based on a partial substring. This is equivalent to using a LIKE clause in a SQL query with surrounding wildcards.

Used to filter results based on a partial substring that matches any value in an array.

Used to filter results based on a case insensitive partial substring. This is equivalent to using a ILIKE clause in a SQL query with surrounding wildcards.

Used to filter results based on a case insensitive partial substring that matches any value in an array.

Used to filter results based on an array of values. This is equivalent to using a WHERE clause in a SQL query with an IN operator

Used to filter results based on a value that is false. This is equivalent to using a WHERE clause in a SQL query with a NOT IN operator.

Used to filter results based on a value less than the specified value.

Used to filter results based on a value less than or equal to the specified value.

Used to filter results based on a value greater than the specified value.

Used to filter results based on a value greater than or equal to the specified value.

Used to filter results based on a value that is null.

Used to filter results based on a value that is not null.

Used to filter results based on a value that is true.

Used to filter results based on a value that is false.

Request Body

{
  "query": {
    "registration_start": "AS876"
  },
  "method": "SELECT",
  "page": 1,
  "per_page": 10,
  "sorts": "registration ASC"
}

Response

{
  "data": [
    {
      "id": 1004501200018020,
      "registration": "AS87640",
      "vin": "VF7X1REVF72378327",
      ...
    },
    {
      ...
    },
    {
      "id": 1004501200018020,
      "registration": "AS87644",
      "vin": "VF7X1REVF72378327",
      ...
    }
  ],
  "has_more": true,
  "page": 1,
  "total_pages": 2,
  "total_count": 18,
  "per_page": 10
}

Tokens

Some endpoints contains information, which is more difficult for us to obtain than others and these endpoints requires available tokens to access. Currently this only applies to our inspections, dmr_data, appraisals and tinglysning_data endpoint, but in the future we might implement more advanced endpoints, which also requires tokens to access. Tokens are associated with your account and will reset every period to the amount included in your active subscription. Unused tokens won't roll over to the next month. See all our subscription plans here.

Endpoint

1GET/v1/tokens

Response

{
  "data": {
    "tokens": 1337
  }
}

Vehicles

Using the vehicles endpoint is free for everyone, however the information is limited to the information shown in the example on the right. By default the vehicle object includes basic vehicle information eg. brand, model, fuel type, mileage, registration status etc. You can get a specific vehicle record by providing either the unique id, vin or registration in the request. When multiple vehicles share the same registration the endpoint will return the most recent vehicle associated with the specified registration. The vehicles endpoint also supports 14 expandable resources including weight, emission, periodic taxes and much more. To use expand your active subscription must include the expand capability. Read more about using expand here. Additionally the vehicles endpoint also supports searching. To use search your active subscription must include the search capability. See search for more information.

Requires: ExpandRequires: Search

Request parameters

The unique vehicle id proided by the Danish Road Traffic Authority (Færdselsstyrelsen).

The vehicle identification number (VIN) of the vehicle.

The license plate (registration) of the vehicle. Danish license plates have the following format 'AB12345'.

The following attributes are expandable. - Inspections - Equipment - Emission - Engine - Weight - Age - Axle - Body - Manufacturer - Driving License - Periodic Taxes - Permits

This parameter is only supported and required when using the search endpoint. Expandable searchable attributes - emission.co2 - emission.co - emission.hc_plus_nox - emission.nox - emission.particles - emission.particle_filter - emission.smoke_density - emission.smoke_density_engine_speed - emission.euronorm - engine.fuel_efficiency - engine.electricity_efficiency - body.color See the search endpoint for more information regarding supported predicates.

This parameter is only supported and required when using the search endpoint. A string representing the name of the attribute you want to group your search results by. This is only available with aggregate functions using our search module. The attributes can be any of the following: - id - registration - vin - first_registration_date - registration_status - registration_status_updated_at - kind - usage - model_year - fuel_type - mileage - extra_equipment - brand_id - model_id - variant_id - version_id - co2 - co - hc_plus_nox - nox - particles - particle_filter - smoke_density - smoke_density_engine_speed - technical_total_weight - total_weight - vehicle_weight - driveable_weight_minimum - driveable_weight_maximum - v_value_air_suspension - v_value_mechanical_suspension - road_train_weight - coupling_device - coupling_device_load_maximum - trailer_with_brakes_weight_maximum - trailer_without_brakes_weight_maximum - trailer_total_weight_maximum - axles - axle_track - pulling_axles - drive_shaft_pressure_maximum - trailer_allowed_pressure_maximum - doors - vin_placement - track_width_front - track_width_rear - passengers - seats_minimum - seats_maximum - standing_passengers_minimum - standing_passengers_maximum - rims_and_tires - fuel_efficiency - electricity_efficiency - top_speed - cylinders - engine_displacement - engine_power - color_id - color - gears - euronorm - ncap_five - last_inspection_date - last_inspection_result - last_inspection_kind - category - engine_code - suitable_for_taxi - eu_version - eu_variant - ec_type_approval - body_type - brand - model - variant - version - inspection_frequency - next_inspection_date - insurance_company - insurance_status - insurance_policy_number - insurance_created_at - cached_at - inspection_invocations - status - status_updated_at - horsepower - mileage_annual_average - energy_class - power_to_weight_ratio - age - electricity_efficiency_measured - battery_capacity - electric_range - plugin_hybrid - automatic_transmission - last_modification - next_inspection_date_estimate - brand_and_model - fuel_type_extended - emission_class - emission_class_id - allowed_in_environmental_zones See the search endpoint for more information regarding group_by.

Response parameters

The unique vehicle id proided by the Danish Road Traffic Authority (Færdselsstyrelsen).

The license plate (registration) of the vehicle. Danish license plates have the following format 'AB12345'.

The vehicle identification number (VIN) of the vehicle.

A string representing the date of the first registration date in the format yyyy-mm-dd

A string representing the current status of the vehicle. The status can be either one of these options: - 'Oprettet' - 'Registreret' - 'Skrottet' - 'Afmeldt' - 'Eksporteret' - 'Slettet' - 'UnderOprettelse' - 'DelvistOprettet' - 'AdministrativOprettelse' - 'HarGennemførtRegistreringssyn'

A string representing the date of the most recent change to the status in the format yyyy-mm-dd

A string representing the current registation status of the vehicle. The registration status can be either one of these options: - 'UnderUdarbejdelse' - 'Registreret' - 'Afmeldt'

A string representing the date of the most recent change to the registration status in the format yyyy-mm-dd

A string representing the kind of vehicle. The kind can be either one of these options: - 'Blokvogn' - 'Påhængsvogn' - 'Lastbil' - 'Motordrevet blokvogn' - 'Stor personbil' - 'Motorcykel' - 'Sættevogn' - 'Motorredskab' - 'Traktor' - 'Traktorpåhængsvogn' - 'Personbil' - 'Stor knallert' - 'Campingvogn' - 'Lille knallert' - 'Varebil' - 'Påhængsredskab'

A string representing the usage of the vehicle. The usage can be either one of these options: - 'Særlig anvendelse' - 'Sygetransport' - 'Godstransport (½ OMS.)' - 'Brandsluknings-/redningskørsel ' - 'Ambulancekørsel' - 'Godstransport privat' - 'Kun godkendt til skov-, landbrug og gartneri' - 'Rutekørsel' - 'Godstransport erhverv' - 'Trækkraft for sættevogn' - 'Beboelse' - 'Privat personkørsel' - 'Skov-, landbrug- og gartnerikørsel' - 'Godstransport' - 'Arbejdskørsel' - 'Særtransport' - 'Buskørsel' - 'Mandskabs-/Materielkørsel' - 'Taxikørsel' - 'Godstransport privat/erhverv' - 'Kørsel for offentlig myndighed' - 'Rustvognskørsel' - 'Kun godkendt til rutekørsel' - 'Limousinekørsel' - 'Privat buskørsel'

A string representing the category of the vehicle. Cagegory M → M1, M2 and M3 Motor vehicles designed and constructed primarily for the carriage of persons and their luggage. - M1: Total weight below 3.500 kg and has a maximum of 9 passengers including the driver. - M2: Total weight below 5.000 kg and can carry more then 9 passengers. - M3: Total weight above 5.000 kg and can carry more than 9 passengers. Cagegory N → N1, N2 and N3 Motor vehicles designed and constructed primarily for the carriage of goods. - N1: Total weight below 3.500 kg. - N2: Total weight below 12.000 kg. - N3: Total weight above 12.000 kg. Cagegory O → O1, O2, O3 and O4 Trailers designed and constructed for the carriage of goods or of persons as well as for the accommodation of persons. - O1: Total weight below 750 kg. - O2: Total weight below 3.500 kg. - O3: Total weight below 10.000 kg. - O4: Total weight above 10.000 kg.

An integer representing the model year of the vehicle.

A string representing the fuel type of the vehicle. The fuel type can be either one of these options: - 'Benzin' - 'Diesel' - 'El' - 'Petroleum' - 'Brint' - 'F-Gas' - 'N-Gas'

An integer representing the mileage of the vehicle.

An integer representing the average mileage per year of the vehicle. The number of years is calculated based on the difference between first_registration_date and last_inspection_date. If either of these are null, the average mileage will also return null. Otherwise the mileage is divided by the number of years.

A string representing the combination of the brand and model of the vehicle. See the brand endpoint for more information and the model endpoint for more information.

A string representing the brand of the vehicle. See the brand endpoint for more information.

A string representing the brand id of the vehicle. See the brand endpoint for more information.

A string representing the model of the vehicle. See the model endpoint for more information.

A string representing the model id of the vehicle. See the model endpoint for more information.

A string representing the variant of the vehicle. See the variant endpoint for more information.

A string representing the variant id of the vehicle. See the variant endpoint for more information.

A string representing the version of the vehicle. See the version endpoint for more information.

A string representing the version id of the vehicle. See the version endpoint for more information.

A string representing the body type of the vehicle. See the body_type endpoint for more information.

A string representing the EU version of the vehicle.

A string representing the EU variant of the vehicle.

A string representing the European Community Type Approval of the vehicle.

A string representing the date of the last inspection in the format yyyy-mm-dd.

A string representing the result of the last inspection. The inspection result can be either one of these options: - 'Godkendt' - 'IkkeFuldstaendigtSyn' - 'IkkeGodkendt' - 'IkkeGodkendtKanGenfremstilles' - 'KanGodkendesVedOmsynAfOmsynsvirksomhed' - 'KanGodkendesVedOmsynAfSynsvirksomhed'

A string representing the kind of the last inspection. The inspection kind can be either one of these options: - 'KontrolSyn' - 'MOT' - 'PeriodiskSyn' - 'RegistreringsSyn' - 'RegistreringssynToldsyn'

A string representing the estimated date of the next periodic inspection in the format yyyy-mm-dd. The date is estimated based on available data and is not guaranteed to be correct. You can use the DMR data endpoint to get the official date of the next periodic inspection. Read more about the frequency of periodic inspections here.

A boolean representing if the vehicles has completed the Euro NCAP test with 5 stars. Read more about NCAP test and stars here.

A string in the format yyyy-mm-dd representing the start date of the current leasing period. Returns null if the vehicle is not currently leased. See leasing periods to get a list of all previous leasing periods.

A string in the format yyyy-mm-dd representing the end date of the current leasing period. Returns null if the vehicle is not currently leased. See leasing periods to get a list of all previous leasing periods.

A comma separated string representing the extra equipment of the vehicle. The extra equipment is more detailed than the equipment resource, but isn't available for all vehicles.

An array of objects representing the inspections of the vehicle. By default the vehicles object will include a shallow version of all inspections with limited information. To include the full inspection object use the expand parameter. See the inspections endpoint for more information. NB: Inspections are only included/available with a paid subscription.

Endpoints

1GET /v1/vehicles/:id
2GET /v1/vehicles/vin/:vin
3GET /v1/vehicles/registration/:registration
4POST/v1/vehicles/search

Response

{
  "data": {
    "id": 1004501200018020,
    "registration": "AS87640",
    "vin": "VF7X1REVF72378327",
    "first_registration_date": "2000-08-14",
    "status": "Skrottet",
    "status_updated_at": "2016-04-18",
    "registration_status": "Afmeldt",
    "registration_status_updated_at": "2016-04-18",
    "kind": "Personbil",
    "usage": "Privat personkørsel",
    "category": "M1",
    "model_year": null,
    "fuel_type": "Benzin",
    "mileage": 407000,
    "mileage_annual_average": 25432,
    "brand_and_model": "CITROËN XANTIA",
    "brand": "CITROËN",
    "brand_id": "10045",
    "model": "XANTIA",
    "model_id": "10045053",
    "variant": "2,0 I 16 V",
    "variant_id": "1004505304",
    "version": "UOPLYST",
    "version_id": "10045053040000000",
    "body_type": null,
    "eu_version": null,
    "eu_variant": null,
    "ec_type_approval": null,
    "last_inspection_date": "2020-04-20",
    "last_inspection_result": "Godkendt",
    "last_inspection_kind": "PeriodiskSyn",
    "next_inspection_date_estimate": "2022-04-20",
    "ncap_five": true,
    "leasing_period_start": null,
    "leasing_period_end": null,
    "extra_equipment": null,
    "inspections": [
      {
        ...
      }
    ]
  }
}

Vehicles

Emission

The emission object is an expandable attribute on vehicles, which you can include by adding the query string ?expand[]=emission to the url of the vehicles endpoint. Included in the response is information about gas-, particle emissions and smoke density. Not all vehicles have this information available - especially older vehicles lack this data. You can see a list of included attributes below. To find information regarding fuel efficiency, fuel type and/or energy efficiency of electric vehicles see engine.

Requires: Expand

Response parameters

A float representing the amount of CO₂ emitted in g/km (Grams per kilometer).

A float representing the amount of CO emitted in mg/km (Milligrams per kilometer).

A float representing the total amount of HC and NOx emitted in mg/km (Milligrams per kilometer).

A float representing the amount of NOx emitted in mg/km (Milligrams per kilometer).

A float representing the amount of particles emitted in mg/km (Milligrams per kilometer).

A boolean indicating if the vehicle has a particle filter.

A float representing the smoke density.

An integer representing the engine's RPM (revolutions per minute) at which the smoke density was measured.

A string representing the energy class of the vehicle. The energy class is calculated based on the fuel type and fuel effiency of the vehicle. The energy class can be either one of these options: - 'A+++' - 'A++' - 'A+' - 'A' - 'B' - 'C' - 'D' - 'E' - 'F' - 'G' Read more about energy classes on the officiel website here.

A string representing the emission class of the vehicle. The emission class can be either one of these options: - '1' - '2' - '3' - '4' - '5'

A string representing the euronorm of the vehicle. The euronorm can be either one of these options: - 'Euro I' - 'Euro II' - 'Euro III' - 'Euro IV' - 'Euro V' - 'Euro VI' - 'Euro VII' - 'Ikke Euro' - 'Ingen Norm' - 'EEV' - 'År 2000 miljønorm' - 'År 2005 miljønorm' - 'Miljønorm 2006 maks 150ccm' - 'Miljønorm 2006 over 150ccm'

A boolean indicating if the vehicle is allowed in environmental zones. The value is calculated based on the fuel_type, kind, registration_date, particle_filter and euronorm of the vehicle. Read more about environmental zones here on miljoezoner.dk

QUERY STRING

1?expand[]=emission

Response

{
  "emission": {
    "co2": 100.0,
    "co": 274.9,
    "hc_plus_nox": 0.0,
    "nox": 25.5,
    "particles": null,
    "particle_filter": false,
    "smoke_density": null,
    "smoke_density_engine_speed": 0,
    "energy_class": "A++",
    "emission_class": "1",
    "euronorm": "Euro V",
    "allowed_in_environmental_zones": true
  }
}

Vehicles

Engine

The engine object is an expandable attribute on vehicles, which you can include by adding the query string ?expand[]=engine to the url of the vehicles endpoint. Included in the response is information about fuel efficiency, top speed, horse power etc. Not all vehicles have this information available - especially older vehicles lack this data. You can see a list of included attributes below. To find information regarding gas- and particle emissions see emission.

Requires: Expand

Response parameters

A float representing the combined fuel efficiency in km/l (kilometers per liter). The value is provided by DMR and accounts for both fossil fuel and electricity.

A float representing the electricity efficiency in wh/km (watt-hours per km).

An integer representing the top speed in km/h (kilometers per hour).

A string representing the primary fuel type of the vehicle.

A string representing the extended fuel type of the vehicle. The extended fuel type include hybrid and plug-in hybrid vehicles. The value is calculated based on the model and variant of the vehicle.

An integer representing the number of gears.

An integer representing the number of cylinders.

A string representing the engine code of the vehicle.

A float representing the engine displacement, sometimes referred to as engine capacity or cc (Cubic Centimeters).

A float representing the engine power of the vehicle in kW (Kilowatt) which is the standard unit used by the European manufacturers. See also horsepower.

A float representing the calculated horsepower of the vehicle based on 1 hp = 0.745699872 kW.

A float representing the calculated power to weight ratio of the vehicle in the unit kW/kg. The value is equal to power_to_weight_ratio = engine_power / driveable_weight_minimum. See the weight endpoint for more information.

QUERY STRING

1?expand[]=engine

Response

{
  "engine": {
    "fuel_efficiency": 23.3,
    "electricity_efficiency": null,
    "top_speed": null,
    "fuel_type": "Benzin",
    "fuel_type_extended": "Benzin",
    "gears": 5,
    "cylinders": 3,
    "engine_code": null,
    "engine_displacement": null,
    "engine_power": 140.0,
    "horsepower": 190.0,
    "power_to_weight_ratio": 0.06
  }
}

Vehicles

Weight

The weight object is an expandable attribute on vehicles, which you can include by adding the query string ?expand[]=weight to the url of the vehicles endpoint. Included in the response is information about weight limits, min/max load, coupling device, max trailer weight etc. Not all vehicles have this information available - especially older vehicles lack this data. You can see a list of included attributes below.

Requires: Expand

Response parameters

An integer representing the maximum allowed total weight for the vehicle according to the manufacturer - this includes passengers, oil, fuel, baggage ect.

An integer representing the maximum allowed total weight for the vehicle according to danish law - this includes passengers, oil, fuel, baggage ect.

An integer representing the weight of the vehicle without passengers, oil, fuel, baggage etc.

An integer representing the minimum drivable weight, which includes the vehicle weight, driver and necessary fluids eg. oil, fuel etc.

An integer representing the maximum drivable weight, which includes the vehicle weight and necessary fluids eg. oil, fuel etc.

An integer representing the v-value of the air suspension.

An integer representing the v-value of the mechanical suspension.

An integer representing the maximum allowed total weight of the vehicle including trailer, passengers, oil, fuel, baggage etc.

A boolean indicating if the vehicle has a coupling device.

An integer representing the maximum allowed load of the coupling device.

An integer representing the maximum allowed weight of a trailer with brakes.

An integer representing the maximum allowed weight of a trailer without brakes.

An integer representing the maximum allowed total weight of a trailer.

A string representing the division of the vehicle. The division can be either one of these options: - 'light' - 'heavy'

QUERY STRING

1?expand[]=weight

Response

{
  "weight": {
    "technical_total_weight": 1340,
    "total_weight": 1340,
    "vehicle_weight": null,
    "driveable_weight_minimum": 943,
    "driveable_weight_maximum": null,
    "v_value_air_suspension": null,
    "v_value_mechanical_suspension": null,
    "road_train_weight": 1570,
    "coupling_device": false,
    "coupling_device_load_maximum": null,
    "trailer_with_brakes_weight_maximum": 200,
    "trailer_without_brakes_weight_maximum": 100,
    "trailer_total_weight_maximum": null,
    "division": "light"
  }
}

Vehicles

Axle

The axle object is an expandable attribute on vehicles, which you can include by adding the query string ?expand[]=axle to the url of the vehicles endpoint. Included in the response is information about number of axles, axle track, drive shaft maximum pressure etc. Not all vehicles have this information available - especially older vehicles lack this data. You can see a list of included attributes below. To find information regarding tires/rims, track width, number of seats/doors etc see body.

Requires: Expand

Response parameters

An integer representing the total number of axles.

An integer representing the axle distance in mm.

A string representing the pulling axles.

An integer representing the maximum pressure on the drive shaft in kg.

An integer representing the maximum pressure on the trailer in kg.

QUERY STRING

1?expand[]=axle

Response

{
  "data": {
    "axle": {
      "axles": 2,
      "axle_track": 2450,
      "pulling_axles": "1",
      "drive_shaft_pressure_maximum": 730,
      "trailer_allowed_pressure_maximum": null
    }
  }
}

Vehicles

Body

The body object is an expandable attribute on vehicles, which you can include by adding the query string ?expand[]=body to the url of the vehicles endpoint. Included in the response is information about tires and rims, track width, number of doors, seats and passengers etc. Not all vehicles have this information available - especially older vehicles lack this data. You can see a list of included attributes below. To find information regarding body type see body type.

Requires: Expand

Response parameters

An integer representing the number of doors of the vehicle.

A string description of the physical vehicle inspection number placement.

An integer representing the track width of the front wheels in mm.

An integer representing the track width of the rear wheels in mm.

An integer representing the maximum number of passengers.

An integer representing the minumum number of seats in the vehicle.

An integer representing the maximum number of seats in the vehicle

An integer representing the allowed minumum number of standing passengers in the vehicle.

An integer representing the allowed maximum number of standing passengers in the vehicle.

A string with a detailed description of rims, tires and axles.

A string representing the color of the vehicle.

QUERY STRING

1?expand[]=body

Response

{
  "body": {
    "doors": 4,
    "vin_placement": "Forrest i motorrum",
    "track_width_front": 1430,
    "track_width_rear": 1415,
    "passengers": 4,
    "seats_minimum": 5,
    "seats_maximum": null,
    "standing_passengers_minimum": null,
    "standing_passengers_maximum": null,
    "rims_and_tires": "1. aksel:175/55R15 77S,15x5J/ET46. 2. aksel: 175/55R15 77S,15x5J/ET46",
    "color": "Rød"
  }
}

Vehicles

Permits

The permits array is an expandable attribute on vehicles, which you can include by adding the query string ?expand[]=permits to the url of the vehicles endpoint. Some vehicles has special permits associated with them. A permit can be granted to vehicles in relation to the use of the specific vehicle. Each permit object consists of a name and a unique id provided by DMR.

Requires: Expand

Response parameters

An integer representing the unique id associated with the permit provided by DMR.

A string representing the name of the permit provided by DMR.

QUERY STRING

1?expand[]=permits

Response

{
  "permits": [
    {
      "id": 1,
      "name": "Synsfri Sammenkobling"
    },
    {
      ...
    }
  ]
}

Vehicles

Age

The age object is an expandable attribute on vehicles, which you can include by adding the query string ?expand[]=age to the url of the vehicles endpoint. The age of a vehicle is calculated on based on the first_registration_date, registration_status and registration_status_updated_at of the vehicle. The age of inactive vehicles is calculated between first_registration_date and registration_status_updated_at whereas active vehicles use the current date. We clasify the vehicle as inactive if the registration_status = 'Afmeldt'. Included in the response is the years and months components of the age object.

Requires: Expand

Response parameters

An integer representing the total number of years of a given age eg. the age 7 years and 6 months would return years: 7.

An integer representing the remaining months of a given age as a number between 0 to 11 eg. the age 7 years and 6 months would return months: 6.

QUERY STRING

1?expand[]=age

Response

{
  "age": {
    "years": 8,
    "months": 6
  }
}

Vehicles

Equipment

The equipment array is an expandable attribute on vehicles, which you can include by adding the query string ?expand[]=equipment to the url of the vehicles endpoint. Most vehicles have different equipment depending on the brand, model, variant and version. Each equipment object consists of a name, quantity and a unique id provided by DMR,

Requires: Expand

Response parameters

An integer representing the unique id associated with the equipment provided by DMR.

A string representing the name of the equipment provided by DMR. The name can be either one of these options: - '1- eller 2-zone klima' - '3 el. flere sæderækker' - '3- eller 4-zone klima' - '6-gear manuel' - 'ABS bremser' - 'affjedret stel (mc)' - 'afstandsradar' - 'Airbags' - 'Bakkamera' - 'brændstoffyr' - 'Dobbeltkabine' - 'elektrisk bagklap' - 'elektrisk lukning af døre' - 'elektron. dæmpere' - 'El-gardiner i bagdøre' - 'El-gardiner i bagrude' - 'el-indstilleligt rat' - 'el-indst. sæder bag' - 'el-opvarmet forrude' - 'el-soltag' - 'ESP (Elektronisk Stabiliserings Program)' - 'fartpilot' - 'faste sidetasker (mc)' - 'firehjulstraek' - 'Glastag' - 'head-up display' - 'HiFi musikanlæg' - 'højrestyring' - 'integreret barnesæde' - 'keramiske skiver' - 'key-less go (nøglefri)' - 'klimaanlæg (Manuel)' - 'kompressor' - 'kurvelys' - 'lædersæder' - 'lang forgaffel (mc)' - 'Linievogter' - 'luftaffjedring' - 'Memory-sæder for' - 'Metalfoldetag' - 'Metallak' - 'Motornummer (mc)' - 'multifunktionsrat' - 'natsyns-udstyr' - 'navigationssystem' - 'niveauregulering' - 'ombygget karrosseri' - 'ombygget stel (mc)' - 'opvarmet rat/styr' - 'original tyverialarm' - 'Parkeringsassistent' - 'Parkeringskontrol bag' - 'Parkeringskontrol for' - 'radio' - 'Ratbetjent gear' - 'ruskind/alcantara' - 'sædemassage' - 'selealarm' - 'skivebremse bag (mc)' - 'skivebremse for (mc)' - 'solcellekøling' - 'sportssæder' - 'stemmestyring' - 'stift stel (mc)' - 'større hjul end 20"' - 'targa' - 'trinløst gear' - 'tunet motor' - 'turbo' - 'u. siderude i v. side af varerum' - 'ventilation i sæder' - 'vognbaneskift-alarm' - 'xenon lys'

An integer representing the quantity of the equipment provided by DMR.

QUERY STRING

1?expand[]=equipment

Response

{
  "equipment": [
    {
      "id": 401,
      "name": "Ratbetjent gear",
      "quantity": 1
    },
    {
      ...
    }
  ]
}

Vehicles

Manufacturer

The manufacturer object is an expandable attribute on vehicles, which you can include by adding the query string ?expand[]=manufacturer to the url of the vehicles endpoint. The Society of Automotive Engineers (SAE) in the US assigns WMIs to manufacturers. We support the most commonly used WMIs, however we can't guarantee this information will be available and accurate for all vehicles. Included in the response is information about the manufacturers name, country and region.

Requires: Expand

Response parameters

A string representing the name of the manufacturer.

A string representing the region of the manufacturer.

A string representing the country of the manufacturer.

QUERY STRING

1?expand[]=manufacturer

Response

{
  "manufacturer": {
    "name": "Mitsubishi Thailand",
    "region": "Asia",
    "country": "Thailand"
  }
}

Vehicles

Driving License

The driving license object is an expandable attribute on vehicles, which you can include by adding the query string ?expand[]=driving_license to the url of the vehicles endpoint. You must have a valid driving licence to legally drive a vehicle in Denmark, which corresponds to the category of your motor vehicle. We support the most common driving license categories, however we can't guarantee this information will be available and accurate for all vehicles. Vehicles are divided into different categories based on their weight and power. See our weight and engine endpoints for more information.

Requires: Expand

Response parameters

A string representing the category of the required driving license to operate the vehicle. The category can be either one of these options: - 'LK' - 'AM' - 'T' - 'M' - 'A1' - 'A1' - 'A' - 'C1' - 'C' - 'B' - 'B+' - 'B/E' Read more about driving license categories here.

QUERY STRING

1?expand[]=driving_license

Response

{
  "driving_license": {
    "category": "B"
  }
}

Vehicles

Periodic Taxes

All registered vehicles pays either vehicle weight tax, green vehicle tax or CO2 vehicle tax. The periodic taxes depends on the vehicle kind, usage and first registration date. Certain vehicles are subject to additional taxes: compensation tax, particle emissions tax, road- and private use tax. The periodic taxes object is an expandable attribute on vehicles, which you can include by adding the query string ?expand[]=periodic_taxes to the url of the vehicles endpoint. Included in the response is an array of periodic taxes which each has a name, amount, payment_frequency and the calculated total_amount. The taxes calculated here is an estimate and we can't guarantee this information will be available and accurate for all vehicles. Currently we only support passenger cars. If you want to calculate the periodic taxes of other vehicles, please use the official periodic tax calculator from the danish motor vehicle agency here.

Requires: Expand

Response parameters

An array of all periodic taxes associated with the vehicle. Vægtafgift → Vehicle weight tax Vehicle weight tax must be paid for private cars first registered in Denmark before 1 July 1997 and for vans first registered in Denmark before 18 March 2009. Vehicle weight tax is calculated on the basis of the vehicle's weight. The heavier the vehicle, the higher the vehicle weight tax. Grøn ejerafgift → Green vehicle tax Green vehicle tax must be paid for private cars (excluding buses) first registered in Denmark between 1 July 1997 and 30 June 2021, and for vans first registered in Denmark during the period between 18 March 2009 and 30 June 2021. Green vehicle tax is calculated on the basis of how far the vehicle's fuel efficiency. The further it can run, the lower the green vehicle tax. CO2-ejerafgift → CO2 vehicle tax CO2 vehicle tax must be paid for private cars and vans (excluding buses) first registered on or after 1 July 2021, irrespective of whether the first registration took place in Denmark or abroad. The CO2 tax is calculated on the basis of the number of grammes of CO2 emitted by the vehicle per kilometre. The less CO2 emitted per kilometre, the lower the tax. Partikeludledningstillæg → Particle emission surcharge A diesel-powered private car or a diesel-powered van with a maximum permitted weight of up to 3,500 kg, and the car is not fitted with an approved particle filter, you must pay an annual particle emissions surcharge. Udligningsafgift → Compensation tax The compensation tax corrects the difference in the tax between petrol and diesel vehicles. When the tax on petrol is increased, the compensation tax is also raised. When the tax on diesel is increased, the compensation tax is lowered.

A float representing the total amount in DKK of all periodic taxes for the vehicle.

A string representing the frequency of the periodic tax. The payment frequency can be either one of these options: - 'quarterly' - 'semesterly' - 'yearly'

QUERY STRING

1?expand[]=periodic_taxes

Response

{
  "periodic_taxes": {
    "taxes": [
      {
        "name": "Grøn ejerafgift",
        "amount": 340.0,
        "payment_frequency": "semesterly"
      },
      {
        "name": "Udligningsafgift",
        "amount": 1420.0,
        "payment_frequency": "semesterly"
      }
    ],
    "total_amount": 1760.0,
    "payment_frequency": "semesterly"
  }
}

Vehicles

DMR Data

Some information isn't available through the weekly XML export eg. next inspection date and insurance information. To get this information you have to manually lookup the vehicle at the official DMR website. The DMR data object is an expandable attribute on vehicles, which you can include by adding the query string ?expand[]=dmr_data to the url of the vehicles endpoint. Included in the response is an object with insurance info and the date of the next inspection. Our server will contact the remote server live. This takes a few seconds to execute and costs 1 token. We suggest that you avoid using this in combination with search and only expand this information for individual vehicles. To improve response times, we cache the response from the remote server for a short time, so subsequent requests are served faster without repeated live queries.

Requires: ExpandRequires: Tokens

Response parameters

A boolean indicating if the DMR service is generally available.

A string representing the name of the insurance company.

A string representing the insurance status.

A string representing the insurance policy number.

A string in the format yyyy-mm-dd representing the day the insurance was created.

A string in the format yyyy-mm-dd representing the date of the next periodic inspection of the vehicle.

A string representing the frequency of inspections for the vehicle.

An array containing any active inspection invocations. Each invocation contains the following attributes: - invocation_type - invocation_created_at - invocation_deadline

A float representing the electricity efficiency measured in wh/km (watt-hours per km)

A float representing the battery capacity in kWh (kilowatt hour).

A float representing the electric range in km (kilometer).

A boolean indicating if the vehicle is a plugin hybrid.

A boolean indicating if the vehicle has an automatic transmission.

A string representing the date of the last inspection in the format yyyy-mm-dd.

A string representing the certificate id of the current leasing period. Returns null if the vehicle is not currently leased. See leasing periods to get a list of all previous leasing periods.

ENDPOINTS / QUERY STRINGs

1GET/v1/vehicles/dmr_data?id=:id
2GET/v1/vehicles/dmr_data?vin=:vin
3GET/v1/vehicles/dmr_data?registration=:registration
4
5?expand[]=dmr_data

Response

{
  "dmr_data": {
    "service_available": true,
    "insurance_company": "Alm. Brand",
    "insurance_status": "Aktiv",
    "insurance_policy_number": "N/A",
    "insurance_created_at": "2021-01-25",
    "next_inspection_date": "2025-01-25",
    "inspection_frequency": "Første gang efter 4 år, herefter hvert 2. år",
    "inspection_invocations": [
      {
        "invocation_type": "PeriodiskSyn",
        "invocation_created_at": "2022-04-26",
        "invocation_deadline": "2022-07-27"
      }
    ],
    "euronorm": "Euro V",
    "electricity_efficiency_measured": 213.0,
    "battery_capacity": 87.0,
    "electric_range": 409.0,
    "plugin_hybrid": false,
    "automatic_transmission": false,
    "last_inspection_kind": "PeriodiskSyn",
    "last_inspection_result": "Godkendt",
    "last_inspection_date": "2020-06-26",
    "leasing_period_start": "2022-05-16",
    "leasing_period_end": "2023-05-16",
    "leasing_period_certificate_id": "491423425567660834"
  }
}

Vehicles

Tinglysning Data

The Tinglysning service is the official Danish registry for rights and obligations on vehicles. The service provides information about the vehicle's liabilities and ownership. The Tinglysning data object is an expandable attribute on vehicles, which you can include by adding the query string ?expand[]=tinglysning_data to the url of the vehicles endpoint. Included in the response is an object with information about the vehicle's liabilities and ownership. Our server will contact the remote server live. This takes a few seconds to execute and costs 1 token. We suggest that you avoid using this in combination with search and only expand this information for individual vehicles. To improve response times, we cache the response from the remote server for a short time, so subsequent requests are served faster without repeated live queries.

Requires: ExpandRequires: Tokens

Response parameters

A boolean indicating if the Tinglysning service is generally available

An array containing all liabilities associated with the vehicle. Each liability contains the following attributes: - date - creditors - debtors - floating_charges - amount - currency

ENDPOINTS / QUERY STRINGs

1GET/v1/vehicles/tinglysning_data?vin=:vin
2
3?expand[]=tinglysning_data

Response

{
  "tinglysning_data": {
    "service_available": true,
    "liabilities": [
      {
        "date": "2023-04-21T08:40:08.137+02:00",
        "creditors": [
          {
            "type": "Person",
            "name": "John Doe",
            "birth_date": "1996-01-01"
          },
          {
            "type": "Person",
            "name": "Jane Doe",
            "birth_date": "1996-12-31"
          }
        ],
        "debtors": [
          {
            "type": "Person",
            "name": "John Doe",
            "birth_date": "1996-01-01"
          },
          {
            "type": "Person",
            "name": "Jane Doe",
            "birth_date": "1996-12-31"
          }
        ],
        "floating_charges": [
          {
            "amount": 100000,
            "currency": "DKK",
            "priority": 1,
            "owners": [
              {
                "type": "Company",
                "name": "Nordea Danmark",
                "cvr": "25992180"
              }
            ]
          }
        ],
        "amount": 100000,
        "currency": "DKK"
      }
    ]
  }
}

Vehicles

Leasing Periods

A vehicle lease is a popular type of auto financing that allows you to “rent” a car from a dealership for a certain length of time and amount of miles. The leasing periods array is an expandable attribute on vehicles, which you can include by adding the query string ?expand[]=leasing_periods to the url of the vehicles endpoint. Included in the response is an array with all known leasing periods ordered by the newest first. Each leasing period object consists of a leasing_period_start and leasing_period_end.

Requires: ExpandRequires: Search

Response parameters

An integer representing the unique identifier of the vehicle.

A string representing the start date of the leasing period in the format yyyy-mm-dd

A string representing the end date of the leasing period in the format yyyy-mm-dd

QUERY STRINGs

1POST/v1/leasing_periods/search
2
3?expand[]=leasing_periods

Response

{
  "leasing_periods": [
    {
      "vehicle_id": 1004501200018020,
      "leasing_period_start": "2022-05-16",
      "leasing_period_end": "2023-05-15"
    },
    {
      "vehicle_id": 1004501200018020,
      "leasing_period_start": "2021-05-16",
      "leasing_period_end": "2022-05-15"
    },
    {
      ...
    }
  ]
}

Vehicles

Supplementary Body Types

The supplementary body types object is an expandable attribute on vehicles, which you can include by adding the query string ?expand[]=supplementary_body_types to the url of the vehicles endpoint. Included in the response is an array of supplementary body types. Each supplementary body type has a name and a unique id provided by DMR.

Requires: Expand

Response parameters

An integer representing the unique id associated with the supplementary body type provided by DMR.

A string representing the name of the supplementary body type provided by DMR. The name can be either one of these options: - 'Åbent lad med sidefjæle' - 'Åbent lad uden sidefjæle' - 'Betonkanon' - 'Bjærgningsanordning' - 'Køleanlæg' - 'Ladlængde 3.00- 3.99 M' - 'Ladlængde 4.00- 4.99 M' - 'Ladlængde 5.00- 5.99 M' - 'Ladlængde over 4.99 M' - 'Ladlængde over 5.99 M' - 'Ladlængde under 3.00 M' - 'Længde max 8 M' - 'Længde over 8 M' - 'Læssebagsmæk' - 'Læssekran' - 'Lukket kasse' - 'Presenningsopbygning' - 'Renovationsaggregat' - 'Sikkerhedsseler eftermonteret' - 'Tank' - 'Tippelad' - 'TMA (energiabsorberende enhed)' - 'Veksellad / container'

QUERY STRING

1?expand[]=supplementary_body_types

Response

{
  "supplementary_body_types": [
    {
      "id": 66,
      "name": "Presenningsopbygning"
    },
    {
      ...
    }
  ]
}

Vehicles

ALPR

Our ALPR (Automatic License Plate Recognition) service is a real-time vehicle recognition system that uses AI to automatically read vehicle license plates. When you request the endpoint the ALPR service will analyze the image and return the vehicle. This takes a few seconds to execute and costs 1 token.

Request parameters

The URL of the image to analyze.