Sam Woodbeck
12/02/2025, 7:39 PMtickets stream. In the Freshservice documentation (https://api.freshservice.com/v2/#view_all_ticket) for the endpoint /api/v2/tickets, they mention that using the API parameter include=stats will embed additional details in the response, including resolved_at and first_responded_at datetime fields. Is there a way to configure the Freshservice connector to pass this API parameters? Or would I need to make a feature request for the connector owner or something?kapa.ai
12/02/2025, 7:39 PMinclude=stats) to the Freshservice API calls for the Tickets stream.[\[Freshservice source\]](https://docs.airbyte.com/integrations/sources/freshservice) The connector docs only describe: - The supported streams (including Tickets) and that some are incremental.[\[Freshservice source\]](https://docs.airbyte.com/integrations/sources/freshservice) - Basic configuration fields (API key, domain, start date).[\[Freshservice source\]](https://docs.airbyte.com/integrations/sources/freshservice) - Changelog entries, which are dependency and format changes, plus adding the Requested Items stream—nothing about exposing extra ticket fields or an include parameter.[\[Freshservice changelog\]](https://docs.airbyte.com/integrations/sources/freshservice#changelog) There is also no mention in the docs of a way to override request parameters for this connector via the UI or configuration, unlike the generic Connector Builder, which supports custom parameter injection using Jinja expressions.[\[Incremental sync\]](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/incremental-sync#custom-parameter-injection) Given that: - You cannot currently configure the Marketplace Freshservice connector (from the docs) to add include=stats yourself. - To get resolved_at / first_responded_at via include=stats, you would need the connector implementation to be updated to pass this parameter and expose these fields in the tickets schema. So the next step would be to open a feature request for the Freshservice connector in the Airbyte GitHub repo, describing that you need tickets to call /api/v2/tickets?include=stats and surface resolved_at and first_responded_at. The Freshservice docs themselves also suggest creating an issue if you need additional endpoints or behavior.[\[Freshservice source\]](https://docs.airbyte.com/integrations/sources/freshservice) If you want to move faster in parallel, another option (not documented for this specific connector) would be to recreate the Freshservice integration using the Connector Builder and configure the query parameters yourself, but that would be a new custom connector rather than changing the existing Marketplace one. The docs only show how to do such custom parameter injection in Builder, not in the Marketplace Freshservice connector.[\[Incremental sync\]](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/incremental-sync#custom-parameter-injection)