Skip to main content
POST
Create a vehicle
Every vehicle gets its own wallet in the organization’s account, named after the license plate, so the vehicle’s fuel and other card purchases are paid from it. The wallet is shared with the users in shared or, when you omit it, with you alone as OWNER. Every required vehicle custom field of the organization must have a value in customFields. A license plate is not unique: registering it again creates another vehicle, with a wallet of its own. Only organization admins can register vehicles. An error from the wallet service — for example when no OWNER in shared is a member of the organization — is returned with its own status, code and origin, and no vehicle is created.

Path Parameters

realmId
string<uuid>
required

ID of your realm.

Format: UUID

organizationId
string<uuid>
required

ID of the organization to register the vehicle in.

Format: UUID

Body

application/json
name
string
required

Display name of the vehicle.

Required string length: 1 - 256
Example:

"Delivery van 07"

licensePlate
string
required

License plate, in the old Brazilian format (ABC1234) or the Mercosul one (ABC1D23). Lowercase, hyphens and spaces are accepted and removed: bra-2e19 is stored as BRA2E19.

Required string length: 1 - 16
Example:

"BRA2E19"

make
string
required

Manufacturer.

Required string length: 1 - 128
Example:

"Fiat"

model
string
required

Model.

Required string length: 1 - 128
Example:

"Fiorino"

year
integer
required

Model year.

Required range: 1900 <= x <= 2100
Example:

2023

shared
object[]

Users who can use the vehicle's wallet. At least one must be an OWNER; a user who is not a member of the organization is left out. Omit it to share the wallet with you alone, as OWNER.

Minimum array length: 1
customFields
object

Values of the organization's vehicle custom fields, keyed by the custom field's slug. Every required one must have a value; null, "" and [] count as no value.


Example: {"cost-center":"CC-1020"}

Example:

Response

Successful response

A vehicle of the organization's fleet.

id
string
required

ID of the vehicle.

Example:

"6710b8e4c9e77b0012a4d6f1"

realmId
string<uuid>
required

ID of the realm the vehicle belongs to.

Example:

"f495ff0c-ab54-4f99-8e92-ca8682e4de9b"

organizationId
string<uuid>
required

ID of the organization the vehicle belongs to.

Example:

"c4bd3f21-dfbd-44e8-8055-68ba15bed410"

name
string
required

Display name of the vehicle.

Example:

"Delivery van 07"

licensePlate
string
required

License plate, upper-cased with no hyphen or space: the old Brazilian format (ABC1234) or the Mercosul one (ABC1D23).

Example:

"BRA2E19"

make
string
required

Manufacturer.

Example:

"Fiat"

model
string
required

Model.

Example:

"Fiorino"

year
number
required

Model year.

Example:

2023

status
enum<string>
required

ACTIVE, or ARCHIVED once the vehicle was archived. An archived vehicle's wallet is blocked.

Available options:
ACTIVE,
ARCHIVED
Example:

"ACTIVE"

external
object
required

The vehicle's dedicated wallet.

customFields
object
required

Values of the organization's vehicle custom fields, keyed by the custom field's slug. Empty when none were set.


Example: {"cost-center":"CC-1020"}

Example:
createdBy
string<uuid>

ID of the user who registered the vehicle.

Example:

"e3553bc1-5e20-4e17-b22a-a796fda0aa99"

updatedBy
string<uuid>

ID of the user who last changed the vehicle.

Example:

"e3553bc1-5e20-4e17-b22a-a796fda0aa99"

createdAt
string<date-time>

When the vehicle was registered.

Example:

"2026-10-17T13:45:12.000Z"

updatedAt
string<date-time>

When the vehicle was last changed.

Example:

"2026-10-17T13:45:12.000Z"