The user
object is included in the Create and Update User endpoints and is included in some webhook callbacks when referring to driver and dispatch events.
Request Data
Below is a list of parameters you can send as part of the user
object, for example, when sending the Create User request.
Read our Data Formatting article for more details about how different parameter types, such as datetime, are formatted and used in Bringg.
Parameter | Description |
---|---|
| Indicates if the user has administrative privileges. |
| Indicates if the user is a dispatcher. |
| Bringg's ID for the group of users within a team. See Get Companies. |
| Your external system's ID for the group of users within a team. See Get Companies. |
| Your external system's ID for the driver's delivery crew, used to coordinate meetups and floating helper tasks during planned routes. |
| Indicates if the user is a driver. |
| The user's email. |
| Name of emergency contact (for use with the Rapid SOS application). |
| Phone number of emergency contact (for use with the Rapid SOS application). |
| The unique identifier for the user in your external system. |
| An array of your external system's IDs for the teams to which the user belongs. |
| The address of the user's "home" base, usually a warehouse or store location. |
| The latitude of the user's "home" base. |
| The longitude of the user's "home" base. |
| The user's preferred language. |
| The user's name. |
| The user's phone number. |
| The ID of the dispatcher or driver's Privileges group, which associates a dispatcher user with a set of authorization flags. |
| Indicates whether the driver uses their own vehicle to determine if mileage should be compensated. |
| Driver capabilities, such as |
| The IDs of the teams to which the user belongs. |
| The driver user role ID in your external systems. Can be used instead of |
| The ID of the user type within Bringg. |