3rd Party: Few ServiceTitan connections are failing with 404 error for the Leads endpoint
Incident
Report for Fivetran
Resolved
This incident has been resolved. We have observed that instance rates are returning to normal levels, and affected connections are syncing successfully.
Incident Summary
Description:
We identified an issue with a few ServiceTitan connections, which are failing with a 404 error for the Leads endpoint.
Timeline:
This issue began on December 16, 2025, at 12:36 UTC and was resolved on December 16, 2025, at 15:55 UTC.
Cause:
The source system introduced a new mandatory query parameter for the Leads API to distinguish externally captured leads from those created internally. Since this parameter was not previously required, API requests without it resulted in 404 errors, leading to connection failures.
Resolution:
We updated our Leads endpoint to include the newly required parameter. The fix has been validated through unit tests and runmock testing, and API calls are now functioning as expected.
Incident Summary
Description:
We identified an issue with a few ServiceTitan connections, which are failing with a 404 error for the Leads endpoint.
Timeline:
This issue began on December 16, 2025, at 12:36 UTC and was resolved on December 16, 2025, at 15:55 UTC.
Cause:
The source system introduced a new mandatory query parameter for the Leads API to distinguish externally captured leads from those created internally. Since this parameter was not previously required, API requests without it resulted in 404 errors, leading to connection failures.
Resolution:
We updated our Leads endpoint to include the newly required parameter. The fix has been validated through unit tests and runmock testing, and API calls are now functioning as expected.
Monitoring
A fix has been implemented and we are monitoring the results.
Identified
The issue has been identified and we are working to resolve it.
This incident affected: Support connectors (ServiceTitan).