Purpose
Returns the contact types available to the adjusting company. Each contact type carries an ID and a flag indicating whether the type represents an attorney. Use this method before any add operation that creates a new contact (e.g., AddClaimContact, AddDeductiblePayment with an inline new payee) so you can supply a valid ContactTypeID or ContactType.
Endpoint
Method:
GetContactTypesSOAPAction (1.1):
"https://ftservices.onlinereportinginc.com/v2/GetContactTypes"Parameter wrapper:
<oParms>
Authentication
Standard credentials apply. See Authentication & Authorization.
Parameters
Name | Type | Required | Description |
| string | yes | Authorized FileTrac system login. |
| string | yes | Password for the login. |
| string | yes | The unique company code provided by FileTrac. |
This method takes no filter parameters.
Response
Returns a list of ContactTypeExtract objects:
Property | Datatype | Description |
| int | System ID of the contact type. Use as |
| string | Display name of the contact type (e.g., |
| boolean |
|
Errors
This method does not produce method-specific business errors. Authentication failures surface via ResponseCode.
Remarks
Contact types are not editable by the adjusting company through the API. All types — system-generated and those imported into FileTrac at the adjusting company's request — are returned.
System contact types align with the
ContactTypeenumeration documented in Section 02. Custom types imported by FileTrac for a specific adjusting company appear in addition.Cache the result. Contact types change infrequently. Caching the list reduces round-trips when adding many contacts in a session.
Prefer
ContactTypeIDoverContactTypename when storing references. Names can drift if FileTrac relabels a type; IDs are stable.
Example Request (SOAP 1.1)
POST /v2/service.asmx HTTP/1.1
Host: ftservices.onlinereportinginc.com
Content-Type: text/xml; charset=utf-8
SOAPAction: "https://ftservices.onlinereportinginc.com/v2/GetContactTypes"<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<GetContactTypes xmlns="https://ftservices.onlinereportinginc.com/v2/">
<oParms>
<Login>integration.svc</Login>
<Password>•••••••••</Password>
<CompanyKey>ACME-AC-001</CompanyKey>
</oParms>
</GetContactTypes>
</soap:Body>
</soap:Envelope>
Example Response (SOAP 1.1)
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<GetContactTypesResponse xmlns="https://ftservices.onlinereportinginc.com/v2/">
<GetContactTypesResult>
<ContactTypeExtract>
<ContactTypeID>1</ContactTypeID>
<ContactType>Insured</ContactType>
<IsAttorneyType>false</IsAttorneyType>
</ContactTypeExtract>
<ContactTypeExtract>
<ContactTypeID>2</ContactTypeID>
<ContactType>Claimant</ContactType>
<IsAttorneyType>false</IsAttorneyType>
</ContactTypeExtract>
<ContactTypeExtract>
<ContactTypeID>3</ContactTypeID>
<ContactType>Attorney</ContactType>
<IsAttorneyType>true</IsAttorneyType>
</ContactTypeExtract>
<ContactTypeExtract>
<ContactTypeID>17</ContactTypeID>
<ContactType>Contractor</ContactType>
<IsAttorneyType>false</IsAttorneyType>
</ContactTypeExtract>
</GetContactTypesResult>
</GetContactTypesResponse>
</soap:Body>
</soap:Envelope>
Related Methods
AddClaimContact— usesContactTypeandContactTypeID.AddDeductiblePayment,AddReservePayment,AddReserveRecovery— all usePayeeContactTypeIDandPayeeContactTypewhen creating a new payee inline.Contact— the contact type from this list appears as theTypefield on every contact record.Enums— the system-defined ContactType enumeration.
