---
title: "Creates a new IMEIConfig and associates it with vehicle"
method: POST
path: "/v1/resourceowner/imeiconfigs3"
tags: ["ResourceOwnerIMEIConfig3"]
---

# Creates a new IMEIConfig and associates it with vehicle

`POST /v1/resourceowner/imeiconfigs3`

## Request

- Base URL: `https://api.automile.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.automile.com/v1/resourceowner/imeiconfigs3`
- Auth: OAuth 2
  - Implicit: `https://api.automile.com/login/`

## Request body

- IMEIConfigCreate3Model
  - `IMEI` string
  - `VehicleId` integer
  - `SerialNumber` string
  - `IMEIDeviceType` 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 255
  - `OrganizationNodeId` integer

## Response `200`

A link in the header is returned to the newly created ImeiConfig

## Other responses

- `403`: Request is forbidden, this could occur if you try to add an IMEI that already exists or if it is not available in our systems. In addition, if the serialnumber to the IMEI device is incorrect
- `500`: Internal server error

---

[API](https://skmtc.dev/automile/apis/automile-api.md) - [All operations](https://skmtc.dev/automile/apis/automile-api/llms.txt) - [OpenAPI document](https://skmtc.dev/automile/apis/automile-api/revisions/56b5b8d6d733?raw)