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:
GetClaimDetailSOAPAction (1.1):
"https://ftservices.onlinereportinginc.com/v2/GetClaimDetail"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. |
| int | yes | The system ID of the individual claim. Obtained from |
Response
Returns a single Claim object (XML element ClaimExtract) with all nested lists populated. The nested lists are:
Nested list | Type | Notes |
| Additional adjusters assigned. | |
| Diary notes. Each note carries an | |
| Lightweight metadata only (ID, title, file name, date, confidential flag). Call | |
| Every contact attached to the claim. | |
| Share arrangements (reinsurance or coverholder splits). | |
| Contracts that apply to this claim. | |
| Invoices generated against this claim. Each invoice carries | |
| Reserves with their | |
| 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.
GetClaimDetailpopulates most nested objects, but note emails requireGetClaimNoteswithIncludeNoteEmails=true, report binaries requireGetClaimReports, and invoice services/expenses requireGetInvoiceDetailper invoice ID. This is a deliberate performance design.Reservesis fully populated here. Unlike notes, reports, and invoices, the reserve sublists (Changes,Payments,Recovery) come back complete inGetClaimDetail.GetClaimDetailis the single-claim deep read. For multi-claim pulls, callGetClaimSummaries(top-level only) orGetUpdatedClaims(lookup keys only).Polling pattern. A common ingestion pipeline polls
GetUpdatedClaims, then callsGetClaimDetailfor 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
GetClaimSummaries— multi-claim list, top-level only.GetUpdatedClaims— claim IDs that changed since a given datetime.GetClaimNotes— call withIncludeNoteEmails=truefor full note emails.GetClaimReports— retrieve binary report file content.GetInvoiceDetail— populateServicesandExpenseson a returned invoice.Claim— the type returned.
