Trendtrack
Trendtrack
DashboardGet API keyIntroduction
Référence API
Référence

Référence API

Parcourez la référence groupée par endpoints pour shops, advertisers, ads, favorites, usage et workspace.

Resource-based navigation

Use the left sidebar to browse the API by resource area instead of endpoint-by-endpoint. Each resource page lists every operation in that group with request and response samples.

Jump to a resource

Shops

Search Shopify stores, pull analytics, and inspect store-level traffic, product, and Meta ad signals.

Ads

Query ad creatives across Meta, TikTok, and Facebook. Filter by status, media type, sort, and pagination.

Advertisers

Look up Meta advertiser pages, their active ads, and aggregate performance signals tracked by Trendtrack.

Brandtrackers

List workspace brandtrackers, resolve brandtrackerId, start with overview, then use /top-ads?sortBy=currentRank for current rank or rankDelta7d|rankDelta14d|rankDelta30d for movers. Scaling/ad-rank are legacy compatibility endpoints.

Discovery

Resolve a brand name, domain, Facebook page ID, or Instagram handle via GET /v1/lookup and pivot to linked brandtracker, advertiser, and shop resource IDs.

Favorites

Read and manage the favorites (saved items) belonging to the authenticated workspace.

Workspace

Retrieve metadata about the workspace attached to the API key making the call.

Usage

Check remaining credits, billing period, and metered consumption for the current workspace.

Identity

Inspect the owner and scopes of the API key presented in the request.

System

Probe public surface endpoints — health, metadata, shell routes, and freshness checks like GET /v1/system/freshness before production traffic.

Emails

Endpoints for email-specific lookups and exports supported by the API.

Common naming and filtering conventions

  • Public API base URL: https://api.trendtrack.io.
  • Public query surfaces use canonical sort fields sortBy and order.
  • GET /v1/ads canonical query param is search; deprecated alias query is accepted for backward compatibility, but sending both search and query in one request returns a conflict validation error.
  • GET /v1/advertisers supports simple categoryIds filters. POST /v1/advertisers/query supports either categoryIds shorthand or pageNiches (not both). Empty {} bodies are valid for the POST query endpoint.
  • GET /v1/shops supports categoryIds, pixelIds, excludePixelIds, shopifyAppIds, and excludeShopifyAppIds filters.
  • POST /v1/shops/query with searchType: "domain" performs exact domain/related-domain matching from a domain or URL (no broad wildcard/text fallback). Use searchType: "shopContains" for broad website text discovery.
  • GET /v1/lookup returns additive signals fields to help disambiguate close matches before metered calls.
  • Workspace top-ads rows are nested objects { brandtracker, ad, metrics } (not a flat ad row).
  • Folder discovery is available on both GET /v1/workspace/folders and GET /v1/brandtrackers/folders.
  • Email endpoints do not expose opens/clicks/conversions/revenue metrics. Email sort fields are discovery/indexing sorts, not “best-performing email” KPIs.
  • For scaling workflows, advertiser reachDelta7d sorting is not supported; use supported advertiser sorts (reach14d, activeAds, etc.) or mover sorts on brandtracker/workspace top-ads.
  • reachPeriod chooses the metric window used by reach/spend thresholds. By itself it does not filter unless paired with minReach, maxReach, or an endpoint-specific reach sort/filter.

Recommended workflow

  1. Start with Getting Started to obtain a key and make a first call.
  2. Confirm Authentication so every subsequent request carries Authorization: Bearer <key>.
  3. For brand/domain/Facebook page ID/Instagram handle questions, call GET /v1/lookup?q=... first (zero-credit), then pivot to the linked brandtracker, advertiser, or shop resource IDs.
  4. For tracked-brand deep dives, use GET /v1/brandtrackers/{brandtrackerId}/overview first.
  5. For rankings, use canonical top-ads calls: GET /v1/brandtrackers/{brandtrackerId}/top-ads?sortBy=currentRank or GET /v1/workspace/top-ads?sortBy=currentRank.
  6. For rank movers, use sortBy=rankDelta7d, rankDelta14d, or rankDelta30d; use reach, reachDelta1d, reachDelta7d, or reachDelta30d for reach rankings.
  7. Treat /scaling-ads and /ad-rank as legacy compatibility endpoints; their ES-backed responses may return an empty trajectory.
  8. For freshness-sensitive historical workflows, check GET /v1/system/freshness (global) and GET /v1/brandtrackers/{brandtrackerId}/snapshots (brandtracker-level readiness).
  9. Keep Credits & Billing, Rate Limits, and Errors open while integrating — you will hit them.
  10. Drill into the resource pages above (or the sidebar) for the exact request shape of each operation.

No in-page playground

The API reference does not ship a hosted playground. Copy the request sample on each operation, swap in your bearer API key, and run it from your own terminal or HTTP client. This keeps the reference fast to scan and avoids surprise network calls while you read.

Return to the docs overview for the guided entry point.

Utiliser Trendtrack avec ChatGPT

Connectez ChatGPT à la Public API Trendtrack via l'endpoint MCP distant de Trendtrack pour analyser en direct les marques, publicités, shops et données d'espace de travail.

Ads

Next Page

On this page

Jump to a resourceCommon naming and filtering conventionsRecommended workflow