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.
@<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!
—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)