Update Driver

POST/v1/drivers/update

Updates a driver's name and/or status. There is no delete/remove endpoint — set status to "removed" instead, which stops the driver from being billed or minted a token, without losing their transaction history.

subWalletBalance cannot be changed here. A driver's sub-wallet only ever changes through Distribute to Driver or actual session billing — there's no direct-set for it on a live fleet. (Sandbox fleets have a separate, explicit balance-set mechanism — see Testing & Sandbox.) Similarly, email isn't updatable — it's the driver's identity key; add a new driver instead if it needs to change.

Auth

Authorization: ApiKey <your fleet's API key> — server-side only.

Request parameters

FieldTypeRequiredDescription
emailstringYesIdentifies which driver to update.
updates.namestringNoNew display name.
updates.statusstringNo"active" or "removed". At least one of updates.name/updates.status must be present.

Example request

curl https://api.lotgrids.com/v1/drivers/update \
  -X POST \
  -H "Authorization: ApiKey lg_live_f_8f21a9.9c2e1b7a..." \
  -H "Content-Type: application/json" \
  -d '{
    "email": "adaeze.driver@fleetco.com",
    "updates": { "status": "removed" }
  }'

Example success response

200 OK
{
  "ok": true
}

Error responses

404 driver_not_found
{ "error": { "code": "driver_not_found", "message": "No driver adaeze.driver@fleetco.com in fleet f_8f21a9." } }
400 invalid_argument
{ "error": { "code": "invalid_argument", "message": "No updatable fields (name, status) were provided." } }