X - v2 API Migration Changes
Updated
X has announced the introduction of the X v2 APIs, encompassing endpoints for all major functionalities supported by the platform. The X v2 API is now X's primary API, and it is the focus of their product investment and innovation. Currently, X is working on replacing the v1 endpoints with their v2 counterparts. While some v2 replacements are already available, the process of updating the remaining endpoints is ongoing from X’s end.
Therefore, as Sprinklr, we have initiated the process to migrate the X endpoints currently being used in Sprinklr to their updated v2 endpoints wherever replacements were available.
In the 19.5 release, we have migrated endpoints based on the official v1 to v2 endpoints mapping announced by X on their website: https://developer.x.com/en/docs/twitter-api/migrate/twitter-api-endpoint-map
While most of the endpoint's migrations only have internal backend changes and do not have any customer-facing changes, some of them do impact the user workflow, which are highlighted below:
Changes in Reporting
As part of the new v2 X endpoints, we do not obtain the source field of an Inbound Message. As a result, the source Name and Source Link of an inbound message will no longer be available, while plotting inbound messages in Reporting. The above changes are displayed in the dashboard shared below:
Changes in Rule Engine
As part of the new v2 X endpoints, we do not obtain the following two fields -
Quick Reply
Quick Reply Response
Hence, as a result, the condition of Template Button Post back in the condition of a Rule will no longer be available while making a Rule in the Rule Engine. The above changes are displayed in the screenshot shared:
Changes in Distributed
The Cover Image URL is not rendered as a response in the v2 APIs. Hence in the distributed product suite, the cover Image for a X Social Account will not be fetched in Sprinklr.
Note: While we are advocating for all current parity gaps in X v2 API to be resolved at the earliest, the strategic decision of X Engineering around prioritization of parity asks will be final and binding. As a consequence, Sprinklr and all other vendors who are part of the TOPP partners as well as all public developers building on X v2 APIs might potentially be impacted by any decisions by X to deprecate/discontinue support for specific endpoints entirely or only partially support the full set of metadata fields received previously from endpoints that do have parity support. Sprinklr will push to ensure maximal continuity of feature support, any decisions by X that result otherwise will be communicated if/when we do receive these confirmed updates from X over the next few months.