The FileTrac SOAP API (ClaimService) is the integration interface for the legacy FileTrac claims management platform. It exposes operations to extract claims, contacts, contracts, invoices, notes, reports, reserves, and users from FileTrac, and to insert or update claims, notes, contacts, payments, recoveries, reserves, and report attachments.
Endpoint
https://ftservices.onlinereportinginc.com/v2/service.asmx
The /v2/ path segment is required. The endpoint without /v2/ reaches the deprecated v1 service, which is retained only for backward compatibility.
Protocol
The API is a SOAP web service over HTTPS. Both SOAP 1.1 and SOAP 1.2 are supported. Every operation page in the WSDL publishes both envelope forms.
Property | SOAP 1.1 | SOAP 1.2 |
|
|
|
Action transport |
|
|
Envelope namespace |
|
|
The service target namespace is https://ftservices.onlinereportinginc.com/v2/. Every operation request and response is qualified under this namespace.
WSDL
The Web Services Description Language file is the authoritative source for operation signatures, parameter and return types, and nested object schemas:
https://ftservices.onlinereportinginc.com/v2/service.asmx?WSDL
Per-operation example envelopes are published at https://ftservices.onlinereportinginc.com/v2/service.asmx?op=<MethodName>. When this documentation conflicts with the live WSDL on a technical signature, the WSDL is correct.
What the API Does
The API exposes 24 operations organized into two categories.
Extract methods (14) return data from FileTrac. They support filtering by claim, file number, client company, policy, date range, or other identifiers. Some return top-level summaries (GetClaimSummaries, GetInvoiceSummaries); others return fully nested objects (GetClaimDetail, GetInvoiceDetail).
Insert/update methods (10) push data into FileTrac. They create or update claims (AddClaim), add nested objects to existing claims (AddClaimContact, AddClaimNote, UploadReport), record financial transactions against deductibles, invoices, and reserves (AddDeductiblePayment, AddInvoicePayment, AddReservePayment, AddReserveRecovery), create or update reserves (AddReserve), and update specific date fields on existing claims (UpdateClaimDates).
The API does not expose user management, account configuration, billing, fee schedule administration, or any system settings. Those are configured inside the FileTrac web UI.
What the API Does Not Do
No authentication-token model. Each request carries
Login,Password, andCompanyKeydirectly. There is no OAuth, no API key, no session token.No SOAP faults for business errors. Failed authentication and most business-rule failures return default-empty results or
0IDs with an error string in a response-message field. SOAP faults are reserved for transport-level failures.No bulk update. Each insert/update method writes one object. Use repeat calls for batches.
No delete operations. Records cannot be removed through the API. Voids on payments and recoveries are recorded by submitting an equal-and-opposite negative-amount transaction.
No webhook or push delivery. Integrators poll
GetUpdatedClaimsto discover changes.
Version History
Version | Date | Description |
1.0.0 | 2013.09.26 | Initial release |
1.0.2 | 2014.06.10 | Added |
1.0.3 | 2014.12.15 | Added |
1.0.4 | 2015.12.30 |
|
1.1.0 | 2016.02.20 |
|
1.1.1 | 2016.02.21 | Added |
1.1.2 | 2016.03.23 | Added |
1.2.1 | 2016.11.02 | Added |
1.2.2 | 2017.03.01 | Added |
1.3.0 | 2017.08.15 | Added Reserve and Payment/Recovery methods |
1.3.1 | 2017.08.30 | Added Invoice Payment method |
1.3.2 | 2017.12.01 | Flood fields added to |
1.3.3 | 2018.01.15 | Appendix II added — |
1.3.4 | 2019.01.25 | Additional Bordereaux datapoints |
1.4.0 | 2019.12.19 | User-level authorization applied |
2.0.0 | 2020.04.30 | API behavior overhaul |
2.0.0 | 2020.10.15 | Documentation updates around claim lookup |
2.0.0 | 2021.01.08 | Date-reference details added |
2.0.1 | 2021.03.21 | Date corrections; access to current version described |
2.0.2 | 2026.01.16 |
|
Relationship to FileTrac Evolve
This API serves the legacy FileTrac platform. The modern FileTrac Evolve platform is a separate product with its own integration interface — a GraphQL API at https://integration-api.ftevolve.dev/graphql. The two APIs are not interchangeable. Code written against this SOAP service will not work against FileTrac Evolve, and vice versa.
If you are evaluating which platform to integrate against, consult Evolution Global. New integrations into FileTrac are still supported; Evolution Global recommends evaluating FileTrac Evolve for greenfield work.
Support
Open a FileTrac Support ticket of ticket type Training – General Help with ticket category Questions for API access requests, integration questions, and bug reports.
Where to Start
For authentication and credential setup, see Authentication & Authorization.
For the complete data model, start at Claim and follow the cross-references through every nested type.
For per-method reference, start with GetClientCompanies and AddClaim.
For end-to-end patterns, see Common Integration Patterns.
For diagnostics, see Error Codes & Response Codes.
