Connector Improvement: Support for Yext "Entities" Endpoint in Fivetran Connector (Deprecation of Legacy "Location" Endpoint)
AnsweredCurrently, the Fivetran Yext connector only supports the legacy "Location" endpoint, which is now deprecated according to https://hitchhikers.yext.com/docs/managementapis/knowledgegraph/legacy. Our organization requires the connector to use the new "Entities" endpoint, which is the recommended and supported method for accessing location data in Yext.
-
When attempting to sync data via the Fivetran Yext connector, we receive a 403 Unauthorized error on the "locations" endpoint, despite our API key having the necessary permissions for the new endpoints.
-
Manual API calls to the "entities" endpoint (and other new endpoints) using the same API key are successful (HTTP 200), confirming that permissions and connectivity are not the issue.
-
The Fivetran support team has confirmed that the "Entities" endpoint is not yet included in the connector and suggested submitting a feature request for this improvement.
Please enhance the Fivetran Yext connector to support the "Entities" endpoint, ensuring compatibility with Yext's current API standards and enabling continued data integration as the legacy "Location" endpoint is phased out.
-
Official comment
Hi Mykyta Holovakin,
Thank you for taking the time to share your feature request regarding the Fivetran Yext connector. We truly appreciate your feedback and the detailed context you've provided.
I’m pleased to inform you that your request to enhance the connector to support the "Entities" endpoint has been added to our backlog. We understand the importance of staying aligned with Yext's current API standards, and we will prioritize this feature.
Please rest assured that we will keep you updated on any developments related to this feature request. Your insights are invaluable to us as we strive to improve our product offerings.
Thank you once again for your contribution.
Best regards,
Syead Mujtaba Imam Rizwi -
Hello again,
It's been a 3 month for now. Did you have a chance to take a look at this feature request?
Thanks,
Mykyta
Please sign in to leave a comment.
Comments
2 comments