### RowDrsPayeeEquip XML Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.loadmaster.tablerows.RowDrsPayeeEquip

This snippet shows an example of the RowDrsPayeeEquip structure in XML format. The order of fields is not guaranteed, and null fields are omitted.

```xml
<drs_payee_equip company_id="..." id="..." default_trailer="..." equipment_count="..." equipment_type_id="..." payee_id="..."/>
```

--------------------------------

### RowDrsPayeeEquip JSON Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.loadmaster.tablerows.RowDrsPayeeEquip

This snippet presents an example of the RowDrsPayeeEquip structure in JSON format. Similar to XML, field order is not guaranteed and null fields are excluded.

```json
{"__type":"drs_payee_equip","company_id":"...","id":"...","default_trailer":"...","equipment_count":"...","equipment_type_id":"...","payee_id":"..."}
```

--------------------------------

### RowMobileService XML Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.loadmaster.tablerows.RowMobileService

An example of the XML structure for the RowMobileService. The order of fields is not guaranteed, and null fields are omitted.

```xml
<mobile_service company_id="..." id="..." ack_drvr_key="..." ack_drvr_lic="..." allow_driver_history_report="..." allow_driver_rec="..." allow_geotab_sso="..." allow_time_off_feature="..." android_app_url="..." apns_certificate="..." apns_password="..." base_url="..." dr_contact_email="..." dr_contact_name="..." dr_contact_phone="..." dr_email_list="..." dr_response="..." driver_arrived_flag="..." driver_settlement_flag="..." drvr_lic_cert="..." enable_begin_end_trips="..." enable_bol_prompt="..." enable_location_rating="..." enable_raterequest="..." excluded_companies="..." gcm_sender_key="..." invite_expire="..." ios_app_url="..." legal_terms="..." legal_terms_name="..." login_expire="..." max_search="..." mobile_branding_id="..." ord_contact_name="..." ord_contact_phone="..." ord_email_list="..." ord_submit_ok="..." ping_birthday="..." ping_equip_issues="..." ping_hiredate="..." ping_license_expire="..." ping_mvr_expire="..." ping_physical_expire="..." proof_of_delivery="..." qualcom_enable="..." rate_request_text="..." require_legal_term="..." require_order_term="..." scac="..." time_off_event_code="..." tracking_email="..." update_mcleod="..." use_mcleod_relay="..."/>
```

--------------------------------

### DBDriver XML Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.lib.data.DBDriver

This section provides an example of the expected XML structure for DBDriver. Note that the order of fields is not guaranteed and null fields are omitted.

```APIDOC
## DBDriver XML Example

### Description
Sample XML structure for DBDriver. Field order is not guaranteed, and null fields are excluded.

### Request Example
```xml
<null addPrimaryKeyStatement="..." additionalCreateStatements="..." afterDDLStatements="..." alterColumnStatment="..." applicationNameConnectionProperty="..." beforeDDLStatements="..." countExpression="..." dateFunction="..." dropColumnStatement="..." dropIndexStatement="..." extraCreateDatabaseSQL="..." fieldDefinition="..." hostNameQueryText="..." identityInsertDisableStatement="..." identityInsertEnableStatement="..." indexSpaceString="..." lOBSpaceString="..." lastCountQuery="..." readOnlyDatabaseCheckSQL="..." readOnlyIsolationLevel="..." renameColumnStatement="..." renameTableStatement="..." sPIDQueryText="..." schemaStatement="..." sequenceValueQueryText="..." substringFunction="..." tableSpaceString="..." transactionCountStatement=""/>
```

### Response Example
(No specific success response defined for this example, assumes the XML itself is the data)

```

--------------------------------

### DBDriver JSON Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.lib.data.DBDriver

This section provides an example of the expected JSON structure for DBDriver. Similar to XML, field order is not guaranteed and null fields are omitted.

```APIDOC
## DBDriver JSON Example

### Description
Sample JSON structure for DBDriver. Field order is not guaranteed, and null fields are excluded.

### Request Example
```json
{
  "addPrimaryKeyStatement": "...",
  "additionalCreateStatements": "...",
  "afterDDLStatements": "...",
  "alterColumnStatment": "...",
  "applicationNameConnectionProperty": "...",
  "beforeDDLStatements": "...",
  "countExpression": "...",
  "dateFunction": "...",
  "dropColumnStatement": "...",
  "dropIndexStatement": "...",
  "extraCreateDatabaseSQL": "...",
  "fieldDefinition": "...",
  "hostNameQueryText": "...",
  "identityInsertDisableStatement": "...",
  "identityInsertEnableStatement": "...",
  "indexSpaceString": "...",
  "lOBSpaceString": "...",
  "lastCountQuery": "...",
  "readOnlyDatabaseCheckSQL": "...",
  "readOnlyIsolationLevel": "...",
  "renameColumnStatement": "...",
  "renameTableStatement": "...",
  "sPIDQueryText": "...",
  "schemaStatement": "...",
  "sequenceValueQueryText": "...",
  "substringFunction": "...",
  "tableSpaceString": "...",
  "transactionCountStatement": "..."
}
```

### Response Example
(No specific success response defined for this example, assumes the JSON itself is the data)

```

--------------------------------

### Sample XML for RowMiscBillHist

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.loadmaster.tablerows.RowMiscBillHist

This is an example of the XML structure for RowMiscBillHist. The order of fields is not guaranteed, and null fields are omitted from service responses. This serves as a structural guide.

```xml
<misc_bill_hist company_id="..." id="..." bill_date="..." bill_type="..." billing_user_id="..." customer_id="..." gp_exported="..." invoice_no="..." invoice_no_string="..." order_id="..." post_key="..." post_module="..." purchase_order_no="..." ready_to_process="..." reference_number="..." remark="..." total_charges="..." total_charges_c="..." total_charges_d="..." total_charges_n="..." total_charges_r="..." totalcharge_and_excisetax="..." totalcharge_and_excisetax_c="..." totalcharge_and_excisetax_d="..." totalcharge_and_excisetax_n="..." totalcharge_and_excisetax_r="..." tw_seg_code="..."/>
```

--------------------------------

### GET /drivers/new

Source: https://tms-dsly.loadtracking.com/ws/docs/services_operation=newDriver&role=-1&service=DriverService

Creates a driver object with all configured defaults set. This object is intended for editing before actual database insertion.

```APIDOC
## GET /drivers/new

### Description
Creates a driver object with all configured defaults set. This doesn't create a record in the database. Instead, callers of this method can edit the returned object and then pass it back to the create method to actually insert the record in the database.

### Method
GET

### Endpoint
/drivers/new

### Parameters
#### Path Parameters
_This method has no path parameters._

#### Query Parameters
_This method has no query parameters._

#### Request Body
_This method does not accept a request body._

### Request Example
```
GET /drivers/new
Host: example.com
Accept: application/json
X-com.mcleodsoftware.CompanyID: 123
```

### Response
#### Success Response (200)
- **RowDriver** (object) - A driver record with all appropriate defaults set.

#### Response Example
```json
{
  "driverId": 0,
  "firstName": "",
  "lastName": "",
  "//... other driver fields with default values ..."
}
```
```

--------------------------------

### PUT /equipmentPreferences/create

Source: https://tms-dsly.loadtracking.com/ws/docs/services_role=-1&service=EquipmentPreferencesService

Creates a new equipment preference.

```APIDOC
## PUT /equipmentPreferences/create

### Description
Creates a new equipment preference.

### Method
PUT

### Endpoint
/equipmentPreferences/create

### Parameters
#### Request Body
- **type** (string) - Required - The type of equipment.
- **carrierId** (string) - Required - The ID of the carrier.

### Request Example
```json
{
  "type": "Flatbed",
  "carrierId": "CAR123"
}
```

### Response
#### Success Response (201)
- **id** (integer) - The unique identifier for the newly created equipment preference.
- **type** (string) - The type of equipment.
- **carrierId** (string) - The ID of the carrier.

#### Response Example
```json
{
  "id": 3,
  "type": "Flatbed",
  "carrierId": "CAR123"
}
```
```

--------------------------------

### GET /comments/{parentRowType}/{parentRowId}

Source: https://tms-dsly.loadtracking.com/ws/docs/services_operation=getComments&role=-1&service=CommentService

Retrieves a list of comments for a given parent row type and row ID. For example, driver BJM01 would be requested as "/D/BJM01", where 'D' represents the parent row type of a driver and 'BJM01' the ID for the driver record. Roles that can access this endpoint are Users, Drivers, Carriers, Carrier Drivers.

```APIDOC
## GET /comments/{parentRowType}/{parentRowId}

### Description
Retrieves a list of comments for a given parent row type and row ID.

### Method
GET

### Endpoint
/comments/{parentRowType}/{parentRowId}

### Parameters
#### Path Parameters
- **parentRowType** (String) - Required - The comment record's parent row type.
- **parentRowId** (String) - Required - The comment record's parent row ID.

### Response
#### Success Response (200)
- **List<RowComments>** (array) - A list of RowComments records.
  - **__commentTypeDescr** (string) - Description of the comment type.
  - **RowUsers** (object) - Represents the entered by user.
    - **__name** (string) - Attribute with the value 'enteredByUser'.

#### Response Example
```json
[
  {
    "__commentTypeDescr": "General Inquiry",
    "RowUsers": {
      "__name": "enteredByUser"
    }
  }
]
```
```

--------------------------------

### GET /equipmentPreferences/new

Source: https://tms-dsly.loadtracking.com/ws/docs/services_role=-1&service=EquipmentPreferencesService

Retrieves information for creating a new equipment preference.

```APIDOC
## GET /equipmentPreferences/new

### Description
Retrieves information or a form for creating a new equipment preference.

### Method
GET

### Endpoint
/equipmentPreferences/new

### Parameters
(No parameters)

### Request Example
(No request body needed for GET)

### Response
#### Success Response (200)
- **data** (object) - Contains fields and structure for creating a new equipment preference.

#### Response Example
```json
{
  "data": {
    "field1": "string",
    "field2": "integer"
  }
}
```
```

--------------------------------

### GET /mcmessages/forms

Source: https://tms-dsly.loadtracking.com/ws/docs/services_role=-1&service=McMessageService

Gets active forms for the specified vendor.

```APIDOC
## GET /mcmessages/forms

### Description
Gets active forms for the specified vendor.

### Method
GET

### Endpoint
/mcmessages/forms

### Parameters
#### Query Parameters
- **vendorId** (string) - Required - The ID of the vendor to retrieve forms for.

### Request Example
(No request body for GET requests)

### Response
#### Success Response (200)
- **forms** (array) - A list of active forms.
  - **formId** (string) - The ID of the form.
  - **formName** (string) - The name of the form.

#### Response Example
```json
{
  "forms": [
    {
      "formId": "form123",
      "formName": "Inspection Form"
    },
    {
      "formId": "form456",
      "formName": "Delivery Receipt"
    }
  ]
}
```
```

--------------------------------

### RowMmsMedia JSON Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_type=com.tms.common.loadmaster.tablerows.RowMmsMedia

This is an example of the JSON structure expected for RowMmsMedia data. The order of fields is not guaranteed, and null fields are omitted.

```json
{"__type":"mms_media","company_id":"...","id":"...","media":"...","media_type":"...","parent_row_id":"..."}
```

--------------------------------

### GET /equipmentPreferences/new

Source: https://tms-dsly.loadtracking.com/ws/docs/services_operation=newEquipPref&role=-1&service=EquipmentPreferencesService

Retrieves the configuration for new equipment preferences. This endpoint does not require any specific roles or parameters.

```APIDOC
## GET /equipmentPreferences/new

### Description
Retrieves the configuration for new equipment preferences. This endpoint does not require any specific roles or parameters.

### Method
GET

### Endpoint
/equipmentPreferences/new

### Parameters
#### Path Parameters
_This endpoint has no path parameters._

#### Query Parameters
_This endpoint has no query parameters._

#### Request Body
_This endpoint does not accept a request body._

### Request Example
```json
{
  "example": ""
}
```

### Response
#### Success Response (200)
- **RowDrsPayeeEquip** (application/xml, application/json) - The configuration details for new equipment preferences.

#### Response Example
```json
{
  "example": "<RowDrsPayeeEquip>...</RowDrsPayeeEquip>"
}
```
```

--------------------------------

### RowMmsMedia XML Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_type=com.tms.common.loadmaster.tablerows.RowMmsMedia

This is an example of the XML structure expected for RowMmsMedia data. The order of elements is not guaranteed, and null fields are omitted.

```xml
<mms_media company_id="..." id="..." media="..." media_type="..." parent_row_id="..."/>
```

--------------------------------

### RowProspectAction JSON Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.loadmaster.tablerows.RowProspectAction

An example of the JSON structure for a RowProspectAction. The order of fields is not guaranteed, and null fields are omitted.

```json
{"__type":"prospect_action","company_id":"...","id":"...","action_date":"...","activity_id":"...","call_length":"...","carrier_id":"...","customer_id":"...","date_due":"...","descr":"...","email":"...","info_packet_id":"...","mark_plan_id":"...","next_act_date":"...","next_act_id":"...","next_action":"...","objection_id1":"...","objection_id2":"...","operations_user":"...","opportunity_id":"...","phone":"...","primary_contact":"...","priority":"...","remarks":"...","salesperson_id":"...","start_date":"...","status":"...","windows_task_id":"..."}
```

--------------------------------

### GET /driverApplications/new

Source: https://tms-dsly.loadtracking.com/ws/docs/services_operation=newApplication&role=-1&service=DriverApplicationService

Creates a new driver application object with default values. This object can be modified and then used to create a database record.

```APIDOC
## GET /driverApplications/new

### Description
Creates a driver application object with all configured defaults set. This doesn't create a record in the database. Instead, callers of this method can edit the returned object and then pass it back to the create method to actually insert the record in the database.

### Method
GET

### Endpoint
/driverApplications/new

### Parameters
#### Path Parameters
_This endpoint has no path parameters._

#### Query Parameters
_This endpoint has no query parameters._

#### Request Body
_This endpoint does not accept a request body._

### Request Example
```json
{
  "example": "No request body"
}
```

### Response
#### Success Response (200)
- **RowDriverApplication** (application/xml, application/json) - A driver application record with all appropriate defaults set.

#### Response Example
```json
{
  "example": "<RowDriverApplication><Field>DefaultValue</Field></RowDriverApplication>"
}
```
```

--------------------------------

### RowProspectAction XML Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.loadmaster.tablerows.RowProspectAction

An example of the XML structure for a RowProspectAction. The order of fields is not guaranteed, and null fields are omitted.

```xml
<prospect_action company_id="..." id="..." action_date="..." activity_id="..." call_length="..." carrier_id="..." customer_id="..." date_due="..." descr="..." email="..." info_packet_id="..." mark_plan_id="..." next_act_date="..." next_act_id="..." next_action="..." objection_id1="..." objection_id2="..." operations_user="..." opportunity_id="..." phone="..." primary_contact="..." priority="..." remarks="..." salesperson_id="..." start_date="..." status="..." windows_task_id="..."/>
```

--------------------------------

### RowMobileService JSON Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.loadmaster.tablerows.RowMobileService

An example of the JSON structure for the RowMobileService. The order of fields is not guaranteed, and null fields are omitted.

```json
{"__type":"mobile_service","company_id":"...","id":"...","ack_drvr_key":"...","ack_drvr_lic":"...","allow_driver_history_report":"...","allow_driver_rec":"...","allow_geotab_sso":"...","allow_time_off_feature":"...","android_app_url":"...","apns_certificate":"...","apns_password":"...","base_url":"...","dr_contact_email":"...","dr_contact_name":"...","dr_contact_phone":"...","dr_email_list":"...","dr_response":"...","driver_arrived_flag":"...","driver_settlement_flag":"...","drvr_lic_cert":"...","enable_begin_end_trips":"...","enable_bol_prompt":"...","enable_location_rating":"...","enable_raterequest":"...","excluded_companies":"...","gcm_sender_key":"...","invite_expire":"...","ios_app_url":"...","legal_terms":"...","legal_terms_name":"...","login_expire":"...","max_search":"...","mobile_branding_id":"...","ord_contact_name":"...","ord_contact_phone":"...","ord_email_list":"...","ord_submit_ok":"...","ping_birthday":"...","ping_equip_issues":"...","ping_hiredate":"...","ping_license_expire":"...","ping_mvr_expire":"...","ping_physical_expire":"...","proof_of_delivery":"...","qualcom_enable":"...","rate_request_text":"...","require_legal_term":"...","require_order_term":"...","scac":"...","time_off_event_code":"...","tracking_email":"...","update_mcleod":"...","use_mcleod_relay":"..."}
```

--------------------------------

### GET /users/new

Source: https://tms-dsly.loadtracking.com/ws/docs/services_role=-1&service=UserService

Creates a new user object with default settings, ready for editing before database insertion.

```APIDOC
## GET /users/new

### Description
Generates a new user object pre-populated with default values. This object can be modified before being submitted to the `create` endpoint.

### Method
GET

### Endpoint
/users/new

### Response
#### Success Response (200)
- **user** (object) - A new user object with default properties.
  - **id** (string) - The user's unique identifier (will be generated upon creation).
  - **name** (string) - Default user name.
  - **email** (string) - Default user email.

#### Response Example
{
  "user": {
    "id": null,
    "name": "New User",
    "email": ""
  }
}
```

--------------------------------

### GET /equipmentPreferences

Source: https://tms-dsly.loadtracking.com/ws/docs/services_operation=getEquipPrefList&role=-1&service=EquipmentPreferencesService

Retrieves a list of equipment preferences.

```APIDOC
## GET /equipmentPreferences

### Description
Retrieves a list of equipment preferences.

### Method
GET

### Endpoint
/websites/tms-dsly_loadtracking_ws/equipmentPreferences

### Parameters
#### Query Parameters
- **carrierId** (String) - Required - The ID of the carrier for which to retrieve preferences.

### Request Example
```json
{
  "carrierId": "someCarrierId"
}
```

### Response
#### Success Response (200)
- **List<RowDrsPayeeEquip>** - A list of equipment preference objects.

#### Response Example
```json
[
  {
    "field1": "value1",
    "field2": "value2"
  }
]
```
```

--------------------------------

### RowContact JSON Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.loadmaster.tablerows.RowContact

An example of the JSON structure for a RowContact. The order of fields is not guaranteed, and null fields are omitted.

```json
{"__type":"contact","company_id":"...","id":"...","comments":"...","contact_name":"...","customer_sequence":"...","detention_contact":"...","ect_uid":"...","email":"...","fax":"...","is_active":"...","mobile_phone":"...","name":"...","parent_row_id":"...","parent_row_type":"...","payable_contact":"...","personal_ref":"...","phone":"...","rapid_alert_notify":"...","rec_interval":"...","rec_next_date":"...","rec_ops_user_id":"...","rec_salesperson_id":"...","sequence":"...","terms_contact":"...","title":"...","type_of":"...","web_access":"..."}
```

--------------------------------

### Equipment Preferences - Create

Source: https://tms-dsly.loadtracking.com/ws/docs/services_operation=createEquipPref&role=-1&service=EquipmentPreferencesService

Creates a new equipment preference entry. This endpoint does not require specific roles for access.

```APIDOC
## PUT /equipmentPreferences/create

### Description
Creates a new equipment preference entry. This endpoint does not require specific roles for access.

### Method
PUT

### Endpoint
/equipmentPreferences/create

### Parameters
#### Request Body
- **newRow** (RowDrsPayeeEquip) - Required - The data for the new row to be created.

### Request Example
```json
{
  "newRow": {
    "field1": "value1",
    "field2": "value2"
  }
}
```

### Response
#### Success Response (200)
- **RowDrsPayeeEquip** (application/xml application/json) - The created equipment preference object.

#### Response Example
```json
{
  "RowDrsPayeeEquip": {
    "field1": "value1",
    "field2": "value2"
  }
}
```
```

--------------------------------

### RowContact XML Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.loadmaster.tablerows.RowContact

An example of the XML structure for a RowContact. The order of fields is not guaranteed, and null fields are omitted.

```xml
<contact company_id="..." id="..." comments="..." contact_name="..." customer_sequence="..." detention_contact="..." ect_uid="..." email="..." fax="..." is_active="..." mobile_phone="..." name="..." parent_row_id="..." parent_row_type="..." payable_contact="..." personal_ref="..." phone="..." rapid_alert_notify="..." rec_interval="..." rec_next_date="..." rec_ops_user_id="..." rec_salesperson_id="..." sequence="..." terms_contact="..." title="..." type_of="..." web_access="..."/>
```

--------------------------------

### Search Drivers by Request Parameters (Example)

Source: https://tms-dsly.loadtracking.com/ws/docs/services_operation=getDriversByAdvancedSearch&role=-1&service=DriverService

This example demonstrates how to search for drivers using query parameters such as state and last home date. It illustrates combining multiple search criteria for precise filtering. The API supports flexible querying by allowing any combination of fields from the location table, with optional prefixes.

```HTTP
GET /drivers/search?driver.state=AL&last_home_date=<=t-30
GET /drivers/search?driver.is_active=Y&orderBy=driver.id+DESC
GET /drivers/search?driver.is_active=Y&recordLength=100&recordOffset=50
GET /drivers/search?driver.is_active=Y&changedAfterDate=t-1
GET /drivers/search?driver.is_active=Y&changedAfterDate=t-1&changedAfterType=Add
```

--------------------------------

### RowCache JSON Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.lib.RowCache

An example of the JSON structure for RowCache. The order of fields is not guaranteed, and null fields are omitted.

```json
{"cachedRow":"..."}
```

--------------------------------

### POD Sample JSON

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.loadmaster.dsp.DriverStopReport%24POD

Example of the expected JSON format for Proof of Delivery (POD) data. The order of fields is not guaranteed, and null fields are omitted.

```json
{
  "image": "..."
}
```

--------------------------------

### GET /customers/new

Source: https://tms-dsly.loadtracking.com/ws/docs/services_operation=newCustomer&role=-1&service=CustomerService

Creates a customer object with all configured defaults set. This object can be edited and then passed to the create method to insert a record into the database.

```APIDOC
## GET /customers/new

### Description
Creates a customer object with all configured defaults set. This doesn't create a record in the database. Instead, callers of this method can edit the returned object and then pass it back to the create method to actually insert the record in the database.

### Method
GET

### Endpoint
/customers/new

### Parameters
#### Path Parameters
_This method has no parameters._

#### Query Parameters
_This method has no parameters._

#### Request Body
_This method does not accept a request body._

### Request Example
```json
{
  "example": "No request body"
}
```

### Response
#### Success Response (200)
- **customer record** (object) - A customer record with all appropriate defaults set.

#### Response Example
```json
{
  "example": "application/xml or application/json representing a customer record"
}
```
```

--------------------------------

### RowCache XML Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.lib.RowCache

An example of the XML structure for RowCache. The order of fields is not guaranteed, and null fields are omitted.

```xml
<null cachedRow="..."/>
```

--------------------------------

### GET /settlements/history/{id}

Source: https://tms-dsly.loadtracking.com/ws/docs/services_operation=getSettlementHistoryById&role=-1&service=SettlementService

Retrieves the settlement history record for a specific ID. Users can access this endpoint to get detailed settlement history.

```APIDOC
## GET /settlements/history/{id}

### Description
Retrieves the settlement history record for the given ID. Users can access this endpoint.

### Method
GET

### Endpoint
/settlements/history/{id}

### Parameters
#### Path Parameters
- **id** (String) - Required - ID of the Settlement History record

### Request Example
```json
{
  "example": "Request details for GET /settlements/history/{id}"
}
```

### Response
#### Success Response (200)
- **RowDrsSettleHist** (application/xml or application/json) - Represents a settlement history record.
  - **__payMethodDescr** (String) - The description of the pay method.
  - **__payeeTypeDescr** (String) - The description of the payee type.
  - **__commodityIdDescr** (String) - The description of the commodity.
  - **__revenueIdDescr** (String) - The description of the revenue code.
  - **RowTractor** (Object) - Represents the tractor associated with the settlement.
  - **RowTrailer** (Object) - Represents the trailer associated with the settlement.
  - **RowDriver** (Object) - Represents the driver associated with the settlement.

#### Response Example
```json
{
  "example": "<RowDrsSettleHist __payMethodDescr=\"Cash\" __payeeTypeDescr=\"Driver\" __commodityIdDescr=\"Apples\" __revenueIdDescr=\"Sales\">
    <RowTractor __name=\"tractor\" />
    <RowTrailer __name=\"trailer\" />
    <RowDriver __name=\"driver\" />
  </RowDrsSettleHist>"
}
```
```

--------------------------------

### RowLocationRatingQuestion JSON Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_type=com.tms.common.loadmaster.tablerows.RowLocationRatingQuestion

An example of the JSON structure for a RowLocationRatingQuestion. The order of fields is not guaranteed, and null fields are omitted.

```json
{"__type":"location_rating_question","company_id":"...","id":"...","displayed":"...","factory":"...","question":"...","sequence":"..."}
```

--------------------------------

### Sample XML for StringList

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.lib.StringList

This is an example of the expected XML structure for a StringList. The order of fields is not guaranteed, and null fields are omitted.

```xml
<null ="..." asString="..." items="..." object="..." object="..."/>
```

--------------------------------

### RowLocationRatingQuestion XML Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_type=com.tms.common.loadmaster.tablerows.RowLocationRatingQuestion

An example of the XML structure for a RowLocationRatingQuestion. The order of fields is not guaranteed, and null fields are omitted.

```xml
<location_rating_question company_id="..." id="..." displayed="..." factory="..." question="..." sequence="..."/>
```

--------------------------------

### Sample EdiLogger XML

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.loadmaster.edi.EdiLogger

This snippet shows an example of the expected XML structure for EdiLogger. The order of fields is not guaranteed, and null fields are omitted in the service response.

```xml
<null companyID="..." listenForSettingsChanges="..." logFileName="..." logLevel="..." logName="..." logPath="..." max="..." numDaysToKeep="..." numberWeeksToKeep="..." printThreadName="..."/>
```

--------------------------------

### Sample JSON for RowData

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.lib.data.RowData

An example of the JSON structure for RowData. The order of fields is not guaranteed, and null fields are omitted.

```json
{"aliasName":"...","blob":"...","boolean":"...","currency":"...","date":"...","dateTime":"...","decimal":"...","distance":"...","field":"...","fieldCount":"...","fieldDataValueObjects":"...","fieldValue":"...","float":"...","int":"...","long":"...","metaData":"...","sQLString":"...","string":"...","tableName":"...","time":"...","volume":"...","weight":"..."}
```

--------------------------------

### POST /driverApplications/makeDriver/{applicationId}

Source: https://tms-dsly.loadtracking.com/ws/docs/services_operation=makeDriver&role=-1&service=DriverApplicationService

Creates a driver from a given driver application. Allows specifying driver ID, city ID, and accepts XML or JSON.

```APIDOC
## POST /driverApplications/makeDriver/{applicationId}

### Description
Create a driver from the given driver application. Roles that can access this endpoint are Users.

### Method
POST

### Endpoint
/driverApplications/makeDriver/{applicationId}

### Parameters
#### Path Parameters
- **applicationId** (String) - Required - application ID of the driver application for which to create the driver

#### Query Parameters
- **driverId** (String) - Optional - driver ID to use when creating the driver row, if not supplied and auto gen is active driver table mask will be used
- **cityId** (String) - Optional - city ID of the city associated with driver. If not supplied city name and zip will be used to look up city, if multiple cities are found the first one will be used.

### Request Example
```json
{
  "applicationId": "string",
  "driverId": "string",
  "cityId": "string"
}
```

### Response
#### Success Response (200)
- **RowDriver** (application/xml or application/json) - the created RowDriver
- **string** - representing failure of the web service call

#### Response Example
```json
{
  "message": "Driver created successfully"
}
```
```

--------------------------------

### Sample XML for RowData

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.lib.data.RowData

An example of the XML structure for RowData. The order of fields is not guaranteed, and null fields are omitted.

```xml
<null aliasName="..." blob="..." blob="..." blob="..." boolean="..." boolean="..." boolean="..." currency="..." currency="..." currency="..." date="..." date="..." date="..." dateTime="..." dateTime="..." dateTime="..." decimal="..." decimal="..." decimal="..." distance="..." distance="..." distance="..." field="..." field="..." fieldCount="..." fieldDataValueObjects="..." fieldValue="..." fieldValue="..." float="..." float="..." float="..." int="..." int="..." int="..." long="..." long="..." long="..." metaData="..." sQLString="..." sQLString="..." string="..." string="..." string="..." tableName="..." time="..." time="..." time="..." volume="..." volume="..." volume="..." weight="..." weight="..." weight="..."/>
```

--------------------------------

### POD Sample XML

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.common.loadmaster.dsp.DriverStopReport%24POD

Example of the expected XML format for Proof of Delivery (POD) data. The order of fields is not guaranteed, and null fields are omitted.

```xml
<null image="..."/>
```

--------------------------------

### legGroup JSON Example

Source: https://tms-dsly.loadtracking.com/ws/docs/types_role=-1&type=com.tms.ws.loadmaster.dsp.LegGroup

An example of the JSON structure for the legGroup. Field order is not guaranteed, and null fields are omitted from service responses.

```json
{"__type":"legGroup","descr":"...","leg":"..."}
```