Glimpse documents two GETs on https://enterprise.meetglimpse.com. /v1/interest returns search interest normalized to 100. /v1/interest_enriched returns absolute search volume. Both take keyword, a two-letter geo (worldwide when omitted), resolution of daily, weekly, or monthly, and phrase_match. That is a Google search-volume product. It is not a multi-source trend API. Trends API is the exit when the next series is not Google search. Curl shapes and mode sit on Trends API vs Glimpse.
Two GET endpoints
Auth is an apikey header. There is no mode field. There is no source field. The path is the product. Interest is the 0-100 index. Enriched is counts.
Glimpse's docs state the search-volume endpoint supports five years of weekly points by default, and that longer spans or other resolutions need an email to [email protected]. Treat that as a sales conversation, not a query parameter.
Trends API history uses get_time_series and source google search. The series is 0-100. Absolute counts, when the source has them, arrive as volume on the same row. Null volume is not a zero score. That distinction is on volume versus score. Do not treat Glimpse interest_enriched and Trends API volume as the same methodology.
phrase_match and topic mids stay on Glimpse
Glimpse phrase_match=true is the quoted-phrase behavior on Trends. Trends API does not expose a phrase_match flag. Send the phrase the source expects.
Topic codes work on Glimpse the way they work on Google (/m/... in the Trends URL). That is still Google. It is not type=Amazon Best Sellers and a category. It is not source=app downloads and a bundle id.
Google search only
Keep Glimpse when finance or SEO wants Google counts, topic mids, and will email for limits. Leave when the same notebook has to join Google to a live board. A live board is get_top_trends with a type string, not a third Glimpse GET. Official Google access, if the shopper wants first-party scale, is a different page: official-grade replacement.