Create Vehicle

Create a new Vehicle record.

Optional fields

Any request field marked nullable in the schema may be omitted from the payload entirely - you don't need to send it as null. On a PATCH (partial update), an omitted field is left unchanged; on a POST it's left unset.

HTTP Request

POST/users/api/v1/vehicles/

Example Response

{
  "id": 0,
  "site": 0,
  "created": "2026-09-08T14:40:50.345Z",
  "modified": "2026-09-08T14:40:50.345Z",
  "uuid": "770bba28-9f80-4d40-9c51-6e022364af91",
  "source_ref": "string",
  "registration_number": "string",
  "branding": "string",
  "branding_date": "string",
  "branding_status": "string",
  "branding_status_date": "string",
  "agents": []
}

NameDescription

id

integer

ID

site

integer

Site

created

string

Created

modified

string

Modified

uuid

string

Uuid

source_ref

nullable

string<= 100 characters

Source ref - A unique reference to use for linking records back to *your* system. NB: This must be unique across the entire Prop Data system, so it's best to use a consistent prefix unique to your integration to avoid conflicts with other api consumers.

registration_number

nullable

string<= 30 characters

Registration number

branding

nullable

string

Branding

Choices: LightFull

branding_date

nullable

string

Branding date

branding_status

nullable

string

Branding status

Choices: NewRebrandedRemovedResigned

branding_status_date

nullable

string

Branding status date

agents

array of integers

Choices: [ 1,2,3...2147483648 ]

Responses

201
400 Bad request body
403 You do not have permission to perform this action
500 Internal server error
503 This website is not active