Twingly review

Twingly sells online media and conversation data through APIs. Rather than being a monitoring dashboard first, it collects material from sources such as news sites, blogs, forums, review sites, podcasts and video channels, then makes that data available to customers’ systems. Its homepage also says customers can request monitoring of their own sources.

The product is split across data types and APIs. News monitoring covers active sources in more than 100 countries. Podcast and video search turns spoken content into searchable text, while the Blog and Forum services collect posts from active blogs and forums. Twingly also offers a Reviews API for online customer reviews and a Dark Web Search API for posts, articles and documents.

That makes Twingly a data supplier for teams that want to build their own search, monitoring or analysis workflows. It is not, based on the published product details, a ready-made analytics suite with a published feature-by-feature dashboard.

Twingly’s clearest advantage is breadth. One provider covers several types of public online content, including news, blogs, forums, reviews, podcasts and video. That could reduce the number of separate data sources a team needs to connect, although the published information does not establish how its coverage compares with other providers.

• News monitoring includes active sources across more than 100 countries, according to the published product details.
• Podcast and video search makes spoken content searchable as text, extending monitoring beyond written pages.
• The Blog and Forum services track active sources and collect posts; Twingly says it can also add new blog sources.
• The Reviews API provides access to online customer reviews, and the Dark Web Search API covers posts, articles and documents.
• Customers can try the data with 100 free requests, according to the available pricing information. Twingly’s homepage also invites customers to request monitoring of their own sources.

The API-first approach may suit teams that already have a system for storing and analyzing data. Custom source monitoring is another useful option for coverage needs that standard source lists may not address, though it costs extra and the fee is not published.

The main buying problem is price opacity. The available pricing information lists no monthly or annual price: paid access is quoted through sales, and the price for custom sources is also not published. Overage costs are not published either, so it is difficult to estimate the bill from the published information.

The free offer is limited to 100 requests, not a published free plan. The listed Custom Enterprise access has usage limits tailored to the customer, with a Search API cap of 5 requests per second and a LiveFeed API cap of 10 requests per second. Those are meaningful constraints for teams planning high-volume collection, and the published details do not say what happens at the limit or what extra usage costs.

Other buying details are missing from the available information: it does not publish source counts by product, update frequency, retention periods or a standard paid package. Pricing confidence is marked low, so confirm the free-request terms, required API access, rate limits and full costs with sales before comparing Twingly with a priced alternative.

Twingly lists 100 free requests, but no published paid starting price. Paid access is quoted through sales, and monthly and annual rates are not published, so there’s no reliable tier-by-tier price comparison or disclosed jump between tiers. The listed enterprise access is custom: the pricing information says Search API access is limited to 5 requests per second and LiveFeed API access to 10 requests per second. Usage limits are tailored to customer needs, but total request allowances are not published.

Budget for extras carefully. Custom sources are available for a fee, with the price not published; overage costs are also not published. That leaves the free requests as the only stated price point, not a predictable operating budget. Ask sales to specify recurring fees, request allowances, source charges, overages and whether the quote changes with monthly versus annual billing before you build around the API. The pricing information is marked low confidence, so confirm all terms directly with Twingly.