Purpose

Creates a new claim within FileTrac, or updates a subset of claim fields on an existing claim. Returns the claim's system ID (claimID) on success, or 0 on failure. AddClaim is the largest method in the API; its envelope contains every field documented in the AddClaim Field Reference, plus a nested <Contacts> wrapper for adding multiple contacts in the same call.

Endpoint

Method: AddClaim
SOAPAction (1.1): "https://ftservices.onlinereportinginc.com/v2/AddClaim"
Parameter wrapper: <oClaim>

Authentication

Standard credentials apply, supplied inside the <oClaim> wrapper alongside the claim fields. See Authentication & Authorization.

Parameters

The full field list — including the U updateable flag for each field, FileTrac UI labels, and notes — is documented in the dedicated AddClaim Field Reference. The list below is a summary of the required parameters and the structural fields integrators need to understand at the method level.

Required parameters

Name	Type	Description
`Login`	string	Authorized FileTrac system login.
`Password`	string	Password for the login.
`CompanyKey`	string	The unique company code provided by FileTrac.
`ClientCompanyID`	int	System ID of the client (carrier) company. Obtain from `GetClientCompanies`. `ClientCompanyName` (exact match) may be substituted, but `ClientCompanyID` is recommended.
`ClientClaimNum`	string	The client's claim number — what appears as Client Claim # in the FileTrac UI.

Field categories (from the field reference)

The envelope groups fields by purpose:

Routing: Branch, prefix, client company, client contact, adjuster, manager, supervisor.
Identification: File numbers, client claim number, claim status, special instructions.
Primary Insured: Name, company, policy, addresses, phones, email — also loads as an Insured contact on the claim.
Secondary Insured, Agent: Both also load as contacts.
Loss Location: Address, county, county tier, latitude/longitude.
Primary Claimant: Name, contact info, gender, SSN, DOB — also loads as a Claimant contact.
Loss Info: Loss date and type, urgency flags, CAT code, description, LOB/ISO/Cause codes, contact and inspection dates.
Coverage: Deductibles (including wind), Coverages A–F and their per-coverage deductibles, endorsements, RCV/ACV/Amount.
Flood: Program, risk, FIRM data, water depths, CWOP reason, flood characteristic, advance payments.
Auto: Year, make, model, VIN, mileage, damages, coverage, deductible, location.
Contacts (nested): Additional contacts attached at creation time via the <Contacts> wrapper.

Contacts wrapper

To add contacts during claim creation, include a <Contacts> element containing one or more nested <Contacts> elements (yes, the outer and inner tag names are both Contacts). Each inner block carries the same fields as AddClaimContact minus the FileTracClaimID.

Response

Returns a single int:

The new claim's claimID (matching FileTracClaimID everywhere else in the API) when successful.
For an update, returns the existing claim's claimID.
0 if the insert or update could not be made.

Like AddClaimNote and UploadReport, this method has a bare-int return signature — no ResponseMessage field is surfaced through the envelope. Diagnostic messages from Appendix I are returned through other channels (logs, internal error tracking).

Errors

Error Message	Cause	Remediation
`ERROR extracting claim data`	The request payload could not be deserialized.	Validate the SOAP envelope against the WSDL.
`ERROR - The companyID supplied is not a valid ID for this adjusting company`	`ClientCompanyID` does not exist.	Call `GetClientCompanies` and use a returned ID.
`ERROR - The companyName supplied does not match any companyName for this adjusting company`	`ClientCompanyName` does not match exactly.	Match the name as it appears in FileTrac, or use `ClientCompanyID`.
`ERROR - Both the companyID and the CompanyName supplied are invalid for this adjusting company`	Neither identifier matched.	Re-fetch via `GetClientCompanies`.
`Branch for ACID not defined`	No default branch is defined and no branch was supplied.	Supply `BranchID` or `BranchName`, or contact FileTrac Support.
`Error in inserting unassigned ClaimRep`	The default UNASSIGNED Claim Rep assignment failed.	Retry; if persistent, contact Support.
`Error in inserting claim`	The claim insert failed at the database layer.	Retry.
`Error in inserting into claimContacts`	A contact created alongside the claim failed to insert.	Validate the `<Contacts>` payload.
`Error in inserting into Message table`	A claim-creation note (from the `Note` parameter) failed to insert.	Retry.
`Error in updating claim`	An update to an existing claim failed.	Confirm the claim exists.
`Error in UPDATING claimContacts`	A contact update failed.	Confirm the contact ID.

Remarks

Insert versus update behavior. AddClaim distinguishes new versus existing by matching on ClientCompanyID + ClientClaimNum. If a claim already exists for that combination, the call updates fields marked U in the field reference and leaves all other fields untouched. If not, a new claim is created.
File # generation. By default, FileTrac generates the FileNumber from the adjustment company's AUTO prefix setting. Supply FileNumber to override. Supplying BranchID or BranchName directs the assignment to a branch-specific prefix when one is configured.
Default Claim Rep. When ClientContactID and ClientContactName are both omitted, the claim is assigned to the adjustment company's default UNASSIGNED Rep.
Insured, Secondary Insured, Claimant, and Agent fields also create contacts. Each pair (e.g., InsuredFName + InsuredLName) creates a corresponding contact of the matching type. The <Contacts> wrapper is for additional contacts beyond these.
Most updateable fields require ClientCompanyID + ClientClaimNum to match for the update to take effect. Without that match, you'd be creating a duplicate claim.
IsAppraisal and AutoMileage are recent additions (2026.01.16). Both are present in the live WSDL. IsAppraisal does not appear in the published Appendix IV; AutoMileage does.
WSDL-only fields. IsAppraisal, PolicySection, PolicyConfirmedDate, ContractID, and AdjusterAssignDate appear in the WSDL envelope but are absent from the published Appendix IV. Treat them as supported integration parameters with WSDL provenance.

Example Request (SOAP 1.1) — abbreviated

POST /v2/service.asmx HTTP/1.1
Host: ftservices.onlinereportinginc.com
Content-Type: text/xml; charset=utf-8
SOAPAction: "https://ftservices.onlinereportinginc.com/v2/AddClaim"<?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>
    <AddClaim xmlns="https://ftservices.onlinereportinginc.com/v2/">
      <oClaim>
        <Login>integration.svc</Login>
        <Password>•••••••••</Password>
        <CompanyKey>ACME-AC-001</CompanyKey>
        <ClientCompanyID>4218</ClientCompanyID>
        <ClientClaimNum>LSM-2026-00874</ClientClaimNum>
        <ClaimDateReceived>2026-05-14</ClaimDateReceived>
        <AdjusterID>3327</AdjusterID>
        <InsuredFName>Daniel</InsuredFName>
        <InsuredLName>Kowalski</InsuredLName>
        <InsuredAddr1>2410 Westheimer Rd</InsuredAddr1>
        <InsuredCity>Houston</InsuredCity>
        <InsuredState>TX</InsuredState>
        <InsuredZip>77019</InsuredZip>
        <PolicyNumber>HO3-LSM-44820</PolicyNumber>
        <PolicyType>HO-3</PolicyType>
        <LossAddr1>2410 Westheimer Rd</LossAddr1>
        <LossCity>Houston</LossCity>
        <LossState>TX</LossState>
        <LossZIP>77019</LossZIP>
        <LossDate>05/09/2026</LossDate>
        <LossType>Wind</LossType>
        <LossDescription>Roof damage from severe wind event 5/9.</LossDescription>
        <Deductible>2500.00</Deductible>
        <CoverageA>250000.00</CoverageA>
        <ClaimDateFirstContact>05/15/2026</ClaimDateFirstContact>
        <IsAppraisal>false</IsAppraisal>
        <Contacts>
          <Contacts>
            <ContactType>Agent</ContactType>
            <ContactIsPrimary>false</ContactIsPrimary>
            <ContactFirstName>Sarah</ContactFirstName>
            <ContactLastName>Henderson</ContactLastName>
            <ContactCompany>Henderson Insurance Group</ContactCompany>
            <ContactOfficePhone>713-555-0125</ContactOfficePhone>
            <ContactEmail>shenderson@hig.example</ContactEmail>
          </Contacts>
        </Contacts>
      </oClaim>
    </AddClaim>
  </soap:Body>
</soap:Envelope>

The full envelope contains every field documented in AddClaim Field Reference. Most fields are optional; only the five required parameters listed above must be present.

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>
    <AddClaimResponse xmlns="https://ftservices.onlinereportinginc.com/v2/">
      <AddClaimResult>881204</AddClaimResult>
    </AddClaimResponse>
  </soap:Body>
</soap:Envelope>

Related Methods

GetClientCompanies — call first to obtain ClientCompanyID.
GetClientContacts — call to resolve ClientContactID if assigning a specific Claim Rep.
GetUsers — call to resolve adjuster/manager/supervisor IDs.
GetContactTypes — required if the <Contacts> wrapper contains custom contact types.
AddClaimContact, AddClaimNote, AddReserve — typical follow-on methods after AddClaim succeeds.
UpdateClaimDates — update first-contact and inspection dates after creation.
AddClaim Field Reference — the complete field list with U updateable flags.
Claim — the resulting type returned by GetClaimDetail.
Common Integration Patterns — end-to-end new-claim creation pattern.