Brandwatch sells Consumer Intelligence suites with quote-based annual contracts. API access sits behind Enterprise tiers or paid add-ons, not a public per-call rate card. This page isolates what developers and procurement teams pay for programmatic Brandwatch access.
Brandwatch (Cision) targets enterprise social listening and consumer intelligence. Developers evaluating programmatic access hit the same friction as with Meltwater or Talkwalker: there is no self-serve API checkout, and sales bundles dashboards, seats, and mention caps into one annual figure. This page separates contract economics from API scope so teams can judge whether Brandwatch's export path fits a trend-only workload.
For the multi-vendor view, see the social listening API pricing comparison. For feature overlap without contract math, see the Brandwatch alternative page.
Brandwatch uses custom annual quotes across three product lines: Consumer Intelligence, Social Media Management, and Influencer Marketing. Pricing inputs that move the quote:
| Factor | Effect on price |
|---|---|
| Product suite | Consumer Intelligence vs SMM vs Influencer bundles |
| Mention or query volume | Higher monthly mention caps raise tier |
| User seats | Dashboard users add to license cost |
| Social channels monitored | Facebook, Instagram, X channel limits per tier |
| Data retention | 1-year vs 2-year archives on public-sector tiers |
| API and export rights | Often Enterprise-only or separate API+ contracts |
Brandwatch does not sell API calls à la carte on its marketing site. A developer needing JSON exports pays for the platform tier that unlocks API keys, even if no analyst logs into the UI.
Official list prices are absent. These anchors come from procurement listings and buyer-reported data through mid-2026. Treat them as benchmarks, not quotes.
| Source | Figure | What it covers |
|---|---|---|
| UK G-Cloud Digital Marketplace (Service ID 917870886671618) | £4,800 per unit per year | Enterprise Consumer Research with REST API access |
| Vendr buyer transactions (2025-2026) | ~$50,000 median contract | Full Brandwatch platform deals, not API-only |
| Third-party review estimates (MakerStack, G2 surveys) | ~$800 - $2,000/month entry | Unverified; sales-led quotes only |
| Brandwatch legal terms (API+ product) | Not priced publicly | 200k mentions/month, 20-client minimum, no UI |
The G-Cloud line is the rare fixed public number. Private-sector buyers in the US and EU should expect sales calls and annual terms. Setup and onboarding fees often run a few thousand dollars on Consumer Intelligence deployments, per Vendr buyer notes.
Brandwatch documents a RESTful Analytics API at developers.brandwatch.com. Typical capabilities:
Rate limits in Brandwatch's software terms cite 30 API calls per 10 minutes on the Analytics API tier. Twitter/X data carries additional restrictions documented in their legal schedules.
The API reflects Brandwatch's mention index. It does not return a single normalized 0-100 trend score across Google Search, TikTok hashtag volume, and Reddit subscribers in one request. Each downstream model maps mention counts to internal signals. That design suits PR teams archiving every brand reference. It is heavier than a trend-only stack that queries keyword demand directly.
Brandwatch's legal product schedule describes an API+ SKU: Analytics API access with one query group, 200k mentions per client per month, and no front-end access, with a minimum subscription of 20 clients. That product targets agencies piping mention data into warehouses, not solo analysts.
Enterprise dashboard contracts (the G-Cloud £4,800/year unit references Enterprise Consumer Research) bundle UI seats with API rights. Teams should confirm during procurement whether API keys are included or billed as add-ons. BuzzSumo API tiers (40,000 calls/month on documented BuzzSumo plans) sit in a separate Brandwatch legal schedule and do not replace Consumer Intelligence exports.
| Workload | Brandwatch path | Trends MCP path |
|---|---|---|
| Weekly keyword demand across Google + TikTok + YouTube | Requires query setup per channel inside Consumer Intelligence; API export on Enterprise | One REST or MCP call per source with get_time_series |
| Live "what is trending now" brief | Saved searches + mention spikes | get_top_trends on Google Trends, X, Reddit feeds |
| Budget floor | Annual contract (benchmarks from ~$10k - $50k+) | 100 free requests/month; paid tiers at pricing |
| Sales cycle | Quote, demo, implementation | API key at account |
Trends MCP does not replicate Brandwatch's influencer marketing module, owned-channel publishing, or multi-year mention archives. It wins on cost and latency when the question is "is this topic growing on search and social?" rather than "capture every post mentioning our brand."
For Meltwater contract benchmarks in the same category, see Meltwater API pricing 2026.
Brandwatch's API path makes sense when:
The API path is harder to justify when:
FAQ