Hi team, I have created an alert and a webhook. I received some informations about the liveboard in the webhook body :

json
                "metricId": {
                    "personalisedViewId": "6e88d3eb-4c22-4a7a-8298-XXX",
                    "pinboardVizId": {
                        "pinboardId": "5ce755a4-92c7-4ccf-bf9d-XXX",
                        "vizId": "bf974e04-9643-4364-afb0-XXX"
                    }
                }

I need to know which filters were used to create this alert (exemple : the company selected), but I don't find any endpoint in the rest api to get informations about a personalisedViewId. How to do that ?

message has been deleted

Solution: You’re correct: there is currently no REST API endpoint that resolves a

personalisedViewId

and returns the saved filter state used when the alert was created (at least not exposed as a direct “get personalized view filters” API in the official docs I could retrieve). So from the webhook payload alone:

json
"metricId": {
  "personalisedViewId": "...",
  "pinboardVizId": {
    "pinboardId": "...",
    "vizId": "..."
  }
}

you can reliably identify: - the Liveboard (

pinboardId

) - the visualization (

vizId

) - the internal personalized view reference (

personalisedViewId

) …but not directly fetch the filter selections (like selected company) via a dedicated REST v2 endpoint for personalized views. If you need those filter values downstream, the practical pattern is: 1. Include the business context in your alert naming/metadata conventions (for example, encode company in title/tag). 2. Or store filter context externally when users create alerts (if you control creation flow). 3. Or infer context by re-querying data for the viz + known candidate filters (best-effort, not exact reconstruction). I could not find this in the official ThoughtSpot documentation. Suggestions: - Double-check your cluster version and release notes: this area can evolve, and an endpoint may appear in newer builds. - If this is critical, raise a ThoughtSpot support/product request specifically for: - “resolve

personalisedViewId

to full runtime filter state” - “include resolved filter tokens in alert webhook payload” - Keep using

pinboardId

+

vizId

as stable IDs for routing logic in your webhook consumer. Docs: - ThoughtSpot REST API v2 overview: https://developers.thoughtspot.com/docs/rest-api-v2 - Data/search APIs (for possible inference workflows): https://developers.thoughtspot.com/docs/fetch-data-and-report-apis - REST API playground: https://try-everywhere.thoughtspot.cloud/v2/#/everywhere/api/rest/playgroundV2_0