Skip to main content

GetClaimDetail

Returns a single claim by ID with every nested list populated — secondary adjusters, notes, reports, contacts, shares, contracts, invoices, reserves.

Purpose

Returns a single claim by ID with every nested list populated — Secondary Adjusters, Notes, Note Emails, Reports, Contacts, Claim Shares, Contracts, Invoices, Invoice Services, Invoice Expenses, Reserves, Reserve Changes, Reserve Recoveries, Reserve Payments, and Inspection Forms. Use it after GetClaimSummaries or GetUpdatedClaims has identified a claim of interest.

Endpoint

  • Method: GetClaimDetail

  • SOAPAction (1.1): "https://ftservices.onlinereportinginc.com/v2/GetClaimDetail"

  • Parameter wrapper: <oParms>

Authentication

Standard credentials apply. See Authentication & Authorization.

Parameters

Name

Type

Required

Description

Login

string

yes

Authorized FileTrac system login.

Password

string

yes

Password for the login.

CompanyKey

string

yes

The unique company code provided by FileTrac.

FileTracClaimID

int

yes

The system ID of the individual claim. Obtained from AddClaim, GetClaimSummaries, or GetUpdatedClaims.

Response

Returns a single Claim object (XML element ClaimExtract) with all nested lists populated. The nested lists are:

Nested list

Type

Notes

SecondaryAdjusters

Additional adjusters assigned.

Notes

Diary notes. Each note carries an Emails sublist that is null in this method — call GetClaimNotes with IncludeNoteEmails=true to populate.

Reports

Lightweight metadata only (ID, title, file name, date, confidential flag). Call GetClaimReports to retrieve binary content.

Contacts

Every contact attached to the claim.

ClaimShares

Share arrangements (reinsurance or coverholder splits).

Contracts

Contracts that apply to this claim.

Invoices

Invoices generated against this claim. Each invoice carries Services and Expenses sublists that are null in this method — call GetInvoiceDetail per invoice ID to populate.

Reserves

Reserves with their Changes, Payments, and Recovery sublists fully populated.

InspectionForms

Form IDs and names only.

Returns null if the claim is not found, or if the authenticated user does not have access.

Errors

This method does not produce method-specific business errors. Authentication failures surface via ResponseCode. A missing or unauthorized claim returns null rather than an error message.

Remarks

  • Two-call pattern for full data fidelity. GetClaimDetail populates most nested objects, but note emails require GetClaimNotes with IncludeNoteEmails=true, report binaries require GetClaimReports, and invoice services/expenses require GetInvoiceDetail per invoice ID. This is a deliberate performance design.

  • Reserves is fully populated here. Unlike notes, reports, and invoices, the reserve sublists (Changes, Payments, Recovery) come back complete in GetClaimDetail.

  • GetClaimDetail is the single-claim deep read. For multi-claim pulls, call GetClaimSummaries (top-level only) or GetUpdatedClaims (lookup keys only).

  • Polling pattern. A common ingestion pipeline polls GetUpdatedClaims, then calls GetClaimDetail for each claim ID returned.

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/GetClaimDetail"<?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>
    <GetClaimDetail xmlns="https://ftservices.onlinereportinginc.com/v2/">
      <oParms>
        <Login>integration.svc</Login>
        <Password>•••••••••</Password>
        <CompanyKey>ACME-AC-001</CompanyKey>
        <FileTracClaimID>881204</FileTracClaimID>
      </oParms>
    </GetClaimDetail>
  </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>
    <GetClaimDetailResponse xmlns="https://ftservices.onlinereportinginc.com/v2/">
      <GetClaimDetailResult>
        <!-- Full top-level Claim fields per the Claim type -->
        <FileTracClaimID>881204</FileTracClaimID>
        <FileNumber>AC-26-001142</FileNumber>
        <ClaimStatus>Open</ClaimStatus>
        <!-- ...all other top-level Claim fields... -->
        <SecondaryAdjusters>
          <ClaimExtractSecondaryAdjusters>
            <ID>9921</ID>
            <UserID>4118</UserID>
            <UserFirstName>Diana</UserFirstName>
            <UserLastName>Park</UserLastName>
          </ClaimExtractSecondaryAdjusters>
        </SecondaryAdjusters>
        <Notes>
          <ClaimNoteExtract>
            <FileTracClaimID>881204</FileTracClaimID>
            <NoteID>552103</NoteID>
            <UserID>3327</UserID>
            <UserFirstName>Linh</UserFirstName>
            <UserLastName>Nguyen</UserLastName>
            <VisibleToClient>Yes</VisibleToClient>
            <NoteTimeStamp>2026-05-15T08:42:11</NoteTimeStamp>
            <Note>Initial contact with insured complete. Inspection scheduled 5/17.</Note>
            <Emails xsi:nil="true" />
          </ClaimNoteExtract>
        </Notes>
        <Reports>
          <ClaimExtractReports>
            <ReportID>117820</ReportID>
            <ReportTitle>Initial Inspection Photos</ReportTitle>
            <ReportFileName>inspection_5_17.pdf</ReportFileName>
            <ReportDate>2026-05-17T14:20:00</ReportDate>
            <Confidential>0</Confidential>
          </ClaimExtractReports>
        </Reports>
        <Contacts>
          <Contact>
            <ID>442101</ID>
            <Type>Insured</Type>
            <Primary>Yes</Primary>
            <FirstName>Daniel</FirstName>
            <LastName>Kowalski</LastName>
            <!-- ...other contact fields... -->
          </Contact>
        </Contacts>
        <Reserves>
          <Reserve>
            <ID>20431</ID>
            <Category>Property</Category>
            <Type>Indemnity</Type>
            <Date>2026-05-15T00:00:00</Date>
            <Updated>2026-05-22T00:00:00</Updated>
            <Incurred>45000.00</Incurred>
            <Changes>
              <ReserveChange>
                <ID>30821</ID>
                <Date>2026-05-22T00:00:00</Date>
                <ChangedFrom>30000.00</ChangedFrom>
                <ChangedTo>45000.00</ChangedTo>
                <Reason>Additional damage discovered during inspection</Reason>
              </ReserveChange>
            </Changes>
            <Payments />
            <Recovery />
          </Reserve>
        </Reserves>
        <InspectionForms />
        <!-- ...other nested lists... -->
      </GetClaimDetailResult>
    </GetClaimDetailResponse>
  </soap:Body>
</soap:Envelope>

Fields and nested lists are abbreviated above. The complete shape is documented under the Claim type reference.

Related Methods

Did this answer your question?