Skip to main content

UpdateClaimDates

Updates the Date of Contact and Date of Inspection on an existing claim. The only API method that updates specific date fields after creation.

Purpose

Updates the Date of Contact and Date of Inspection on an existing claim. This is the only API method that updates specific date fields after a claim is created — other fields are written via AddClaim (with the U updateable flag) or remain immutable.

Endpoint

  • Method: UpdateClaimDates

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

  • Parameter wrapper: <oDates>

Authentication

Standard credentials apply, supplied inside the <oDates> wrapper. 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

System ID of the claim.

DateOfContact

dateTime

no

Date of first contact with the insured.

DateOfInspection

dateTime

no

Date of the property inspection.

At least one of DateOfContact or DateOfInspection should be supplied. Sending neither effectively performs a no-op.

Response

Returns a complex UpdateClaimDatesResult:

Field

Datatype

Description

ClaimID

int

The claim ID on success. 0 on failure.

ResponseMessage

string

Success or a failure-identifying string.

Errors

This method does not produce documented error strings in Appendix I. Common failure modes:

  • Invalid FileTracClaimIDClaimID returns 0.

  • Authentication failure surfaces via ResponseCode.

Remarks

  • Both dates can be updated in one call. Supplying only one leaves the other unchanged.

  • The same dates can be set on claim creation by passing ClaimDateFirstContact and ClaimDateInspection to AddClaim. UpdateClaimDates exists for the case where the dates are not known at creation time.

  • No retry-safe idempotency. Re-sending the same payload simply re-writes the same dates. This is harmless but not necessarily intentional.

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/UpdateClaimDates"<?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>
    <UpdateClaimDates xmlns="https://ftservices.onlinereportinginc.com/v2/">
      <oDates>
        <Login>integration.svc</Login>
        <Password>•••••••••</Password>
        <CompanyKey>ACME-AC-001</CompanyKey>
        <FileTracClaimID>881204</FileTracClaimID>
        <DateOfContact>2026-05-15T08:42:00</DateOfContact>
        <DateOfInspection>2026-05-17T14:20:00</DateOfInspection>
      </oDates>
    </UpdateClaimDates>
  </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>
    <UpdateClaimDatesResponse xmlns="https://ftservices.onlinereportinginc.com/v2/">
      <UpdateClaimDatesResult>
        <ClaimID>881204</ClaimID>
        <ResponseMessage>Success</ResponseMessage>
      </UpdateClaimDatesResult>
    </UpdateClaimDatesResponse>
  </soap:Body>
</soap:Envelope>

Related Methods

  • AddClaim — accepts ClaimDateFirstContact and ClaimDateInspection at creation time.

  • GetClaimDetail — verify the dates were applied.

  • ClaimDateOfContact and DateOfInspection on the returned claim are the fields this method updates.

Did this answer your question?