Skip to main content
Omnitracs Knowledge Base

Create Driver



This web service is deprecated because it does not allow the driver's first and last name to be supplied as discreet attributes. All customers are advised to use the newer createDriver2 service in order to provide the driver's first and last name.

Doing so is especially important for HOS customers. Note that this service will not work for HOS customers that enable the Entity Maintenance Bridge or for non-HOS customers whose legacy data is certified compliant with Omnitracs One.

Creates a driver entry on the Services Portal given a driver identifier, the driver's name, a global login password, and an optional Performance Monitoring login password.  A driver is created in both QTRACS and Performance Monitoring.

void createDriver(String driverId, String driverName, String driverLogin, String sensortracsLogin) throws WSException

  • driverId: A string containing a unique driver identifier. 4-10 characters in length.
  • driverName: A string containing the name of the driver being created.
  • driverLogin: A string containing the login password entered by the driver on the mobile device.  Passwords are alphanumeric strings with a maximum length 8.
  • sensortracsLogin: A string containing the Performance Monitoring login password entered by the driver on the mobile device.  Performance Monitoring passwords are strings containing all digits of maximum length 9.


Authorization Requirements


The credentials supplied with this method call (as specified in the accompanying WS-Security header) must be authorized to the following application(s) and their associated role-based permissions.

Required Application Licenses
- Remote Integration

Required User Permissions
- Can use QTRACS
- Can set up drivers
- Can use Performance Monitoring
- Can maintain vehicles and drivers

- Can see drivers

Customer integrators are authorized to their own company's data only.


Sample XML Request


Only the SOAP body is shown. To see a sample SOAP Envelope and Header, click here.




      <driverName>John Adams</driverName>







Sample XML Response


An empty response conveys success. If there was an error, an exception would have been thrown.








001 Unknown Error.
002 Required field not specified. (This error will be thrown if the EMB is enabled.)
003 Company not authorized for integration.
004 User is not authorized.
005 Driver already exists.
006 Driver ID invalid.
007 Driver Name invalid.
008 Driver Login Password invalid.
009 Performance Monitoring Login Password invalid.
010 Driver ID and Performance Monitoring Login Password cannot be the same.

  • Was this article helpful?