Introduction

We allow member to register his cars - e.g. for some benefits related to parking.

The number of cars member may register is limited - see: configuration.

Car is identified by its registration number. We require the number to be valid according to format specific in
the country it is registered in. We always try to normalize the provided number to a string without any whitespace or
special characters like '-'.

The car is treated as valid/active for specific number (see: configuration)
of days after the registration. It may be automatically deleted after this time.

The member may renew the car using this API method.

Member Car Model

Example

{
  "id": 5813951,
  "country": "NO",
  "registration_number": "AB12345",
  "color": "white",
  "make": "Toyota Corolla",
  "expires_at": "2024-11-02T15:12:59.189512Z",
  "created_at": "2023-11-03T15:12:59.190629Z",
  "updated_at": "2023-11-03T15:12:59.190629Z"
}

Definition

Key	Type	Readonly?	Required?	Description
id	integer	yes	yes
country	string	yes	yes	Country in which the car is registered (currently implied from LC settings)
registration_number	string	no	yes	I.e. license plate number. Normalized to have no whitespace or special characters (like `-`)
color	string	no	no	Must comply to the supported list - see here
make	string	no	no	Make of the car
expires_at	datetime	no[^1]	yes	Date after which the car is treated as no longer active and must be renewed
created_at	datetime	yes	yes
updated_at	datetime	yes	yes

Registration Number (LPN) normalization

Across system, LPN is always normalized to a standardized form.

Upon persisting whitespace is removed and a-z characters are converted to uppercase.

This also happens during searches and comparison, so 'AB12345' == 'ab 12345' == 'AB12345'

Member Car Model#

Example#

Definition#

Registration Number (LPN) normalization#

Member Car Model

Example

Definition

Registration Number (LPN) normalization