Fleet
Upsert Driver
Changed onCreate or update a driver in your internal fleet, keyed on your own externalIdentifier. There is no separate create vs. update call — sending the same externalIdentifier again updates the existing driver. The response's created field tells you which happened. To disable a driver, upsert with isShiftActive: false (or enabled: false) — there is no separate delete/disable call.
put/v1/fleet/drivers/upsert
Request
- Base URLhttps://api.sandbox.usenash.com
- Authnone declared
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Request body
Changes
- info
endpoint added
- info