Hitting staging version of an Answers experience with liveAPI

Search
1

Hi, I was wondering if it is possible to hit the liveAPI endpoint for answers vertical search for a staging version of an experience. I’ve tried including the query param experienceVersion=STAGING but it looks to me like it’s still hitting prod.

Here’s a link to the request: https://liveapi.yext.com/v2/accounts/me/answers/vertical/query?v=20211213&retrieveFacets=true&input=Arizona&facetFilters={“c_gs_q2_composite”:[{“c_gs_q2_composite”:{“$eq”:“English”}}]}&api_key=4f3a51f873c14be7f138319e87075824&experienceKey=bankers-life-guided-agent-search&verticalKey=index&experienceVersion=STAGING

And here’s a link to the config: https://www.yext.com/s/1850866/answers/experiences/configuration/bankers-life-guided-agent-search/editConfigInteractive#verticals

On prod there are only 3 facet categories (seen in the request) but we changed the experience on staging to have 9, but this isn’t being reflected in the json response. Just for the record, we checked:

  • STAGING/PROD are pointing to different config versions (57/54)
  • The diff between those config versions looks how I’d expect with the facets being added
  • There are entities that get returned in search results that have data in the newly faceted fields
  • The config change was 3 days ago so I don’t think it’s just a delay

Update: Since writing this, we changed the number of facets on prod from 3 to 4, and it seems to be already reflected in the response, so this doesn’t seem like a delay issue.

Thanks!

2

Hey Cory,

Try using “version=STAGING” as the query param instead of “experienceVersion=STAGING”. I think that should do the trick!

Let me know if that helps,
DJ

3

Hi DJ,

This seems to do the trick. Thanks so much!

1 Like