Liquid M
LiquidM Technology GmbH is a Berlin-based demand-side platform for programmatic advertising, backed by Earlybird. Its platform at platform.liquidm.com exposes two developer surfaces: a Reporting API that returns the same data as the platform's Visual Reports UI, split across more than thirty dimensions (campaign, ad, site, domain, device, geo, audience) and thirty-plus metrics (impressions, bids, bid requests, clicks, CTR, win rate, eCPM, conversion funnels, video quartiles); and a campaign Management API covering campaigns, budgets and ads. LiquidM publishes a first-party MIT-licensed JavaScript client for the Management API and an example Ruby client for the Reporting API from a 100-repo public GitHub organization. The liquidm.com marketing domain now redirects to Equativ, though the platform host and its APIs remain reachable.
Liquid M publishes 5 APIs on the APIs.io network, including Ads API, Authentication API, Budgets API, and 2 more. Tagged areas include Company, Advertising, AdTech, Demand-Side Platform, and Programmatic Advertising.
Liquid M’s developer surface includes developer portal, signup flow, authentication, code examples, and 16 more developer resources.
Kin Score
APIs 5
Individual APIs this provider publishes, each with its own machine-readable definition.
Liquid M Ads API
The Ads API from Liquid M — 1 operation(s) for ads.
Liquid M Authentication API
Auth token issuance for the Reporting API.
Liquid M Budgets API
The Budgets API from Liquid M — 1 operation(s) for budgets.
Liquid M Campaigns API
The Campaigns API from Liquid M — 1 operation(s) for campaigns.
Liquid M Reporting API
Visual report queries across dimensions and metrics.
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
liquid-m-mcp.yml
MCP SERVERJSON Schema 1
Standalone JSON Schema definitions for this provider's data models.
LiquidM Visual Report
JSON SCHEMAExamples 1
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 1
The organization behind the API