Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Unanswered
← How to test aggregator locally

I am not exactly sure what you are asking but dev.q2api.com, stage.q2api.com, and prod.q2api.com are all the same repository underneath. There will be almost no differences between the environments.

Posted 3 years ago
Trey Teter
124 × 2 Administrator
0

@<1293619705470259200|Trey Teter> Sorry I should of given more context. Lets say I've down a reverse lookup for a user and am now trying to make an aggregator call and I'm running my extension locally... should I be calling the dev environment I assume? Does it matter which environment I'm calling or is the q2 DB shared between dev and staging?

I'd test it out myself but dev is down. Thanks!

— Draden Gaffney   3 years ago
0

Hi Draden,
For aggregator calls, you are going to want to use https://agg-dev.q2api.com/v2 instead of https://dev.q2api.com/v2 (see Aggregator Documentation for more info. You should be able to use the dev environment in your sandbox, assumming that you are passing in the expected scopes (your application would need to point to your dev environment and have the usage token and target endpoints toggled as scopes)

— Solene Sossah   3 years ago
25 Views
0 Answers
3 years ago
3 years ago