Skip to main content
This page tracks notable changes to the Everflow API, SDKs, and developer documentation. Check back regularly for updates on new endpoints, breaking changes, and documentation improvements.
2026-06-15
MCP

MCP Server — continuous improvements

A batch of refinements to the read-only MCP tools, focused on counting, scoped summaries, metric clarity, and timezone correctness.
  • count_entities — a new generic tool that returns only the match count for a type + filter set, with no records or pagination. Use it for “how many” questions instead of paging list_offers / list_affiliates / list_entities and tallying. See count_entities.
  • run_network_summary entity filters — scope the headline totals to specific offer, affiliate, advertiser, creative, or campaign (pipe for OR). Combined with include=comparison, this answers “is offer 91 up or down vs last week?” — the filter is applied to the comparison period too. See run_network_summary.
  • get_report_schema metric definitions — the response now includes metric_definitions, one entry per metric with { name, description, unit, formula, is_custom }, including this network’s user-defined custom metrics. It is the source of truth for “what metrics exist” and “how is <metric> calculated”. See get_report_schema.
  • Metric filters & percent metricsrun_performance_report accepts metric_filters (e.g. clicks>100,cvr<2, invalid_clicks<=0) on aggregated rows. cvr, ctr, and margin are percentages (2.84 = 2.84%); roas is a ratio. Metric descriptions/formulas are now exact.
  • Network timezone & currency defaultsrun_performance_report, run_network_summary, and search_activity now default to the network’s timezone and base currency (matching the Everflow portal) instead of UTC/USD when those parameters are omitted.
  • Raw-event truncation hints — when search_activity hits its cap it returns truncated (and total_matching for clicks) plus a note steering to run_performance_report (e.g. dimensions=conversion_error_code) for counts and breakdowns.
2026-06-10
APIMCP

Sub and advertiser parameters extended from 5 to 10

Tracking now supports sub1sub10 affiliate sub-parameters and adv1adv10 advertiser parameters everywhere the first five were accepted. Existing integrations are unaffected — the new parameters are optional and omitted from payloads when empty.The expansion applies across every surface:
  • Tracking links and API endpoints — click and conversion endpoints accept and return the full range (600-char limit per value, unchanged)
  • Reporting — available as filters and per-record fields on clicks, conversions, impressions, exports, and scheduled reports
  • JavaScript SDKEF.click(), EF.conversion(), and EF.impression() accept the new parameters
  • Webhooks & Firehoseconversion webhook and Firehose payloads carry sub1sub10 and adv1adv10
  • MCP Serverrun_performance_report, search_activity, and the event entity types filter on the full range; see Events & Attribution, the new home for click, conversion, and transaction lookup documentation
2026-06-08
MCP

MCP Server — transaction lookup and tool consolidation

One capability added and four tools consolidated, with no net growth in the tool list.
  • Transaction lookupget_entity(type="transaction", id="<transaction ID>") returns the full attribution chain in one call: the click, its conversions (each with attribution_method), pixel-fire logs, and on-hold conversions. See get_entity.
  • search_activity replaces search_clicks and search_conversions — set type to click or conversion. Same filters and data.
  • Deprecationsget_click, get_conversion, search_clicks, and search_conversions are now served via get_entity / search_activity. They remain fully callable for backward compatibility but are no longer listed. See Deprecated tools for the migration table.
2026-06-02
MCP

MCP Server — multi-value filters for performance reports

run_performance_report now matches multiple IDs for a single filter in one query. Separate values with a pipe — offer:1|2|5 — or repeat the key (offer:1,offer:2); both return all of the listed entities together instead of requiring a separate report per ID.
2026-05-19
MCP

MCP Server — new entity types

7 additional types are now supported by get_entity, list_entities, and get_entity_schema: employee, category, channel, label, affiliate_tier, offer_url, and advertiser_event. The total number of supported entity types is now 27.
2026-04-30
API

Update Conversion Notes endpoint documented

Documentation added for the existing PUT /networks/reporting/conversions/{conversionId}/notes endpoint, which lets you attach free-form notes to a conversion. The endpoint itself is unchanged — only the docs are new.
  • View the Update Conversion Notes endpoint reference (Network API → Conversion Updates)
  • Pass an empty string to clear existing notes
  • Returns the full updated conversion record in the response
2026-04-23
MCP

MCP Server documentation added

A new MCP tab has been added to the developer hub covering the Everflow Model Context Protocol (MCP) Server — a native integration for AI assistants (Claude, Cursor, Windsurf, and others) that gives LLMs direct, structured access to your Everflow data without custom API wrappers.
  • Overview — what the MCP Server is and how it works
  • Quickstart — step-by-step setup for Claude Desktop, Cursor, and Windsurf
  • Tools reference — all 16 read-only tools with full parameter, dimension, filter, and metric tables
  • Prompt templates — ready-to-use prompts for common workflows
  • Examples — real conversational walkthroughs
  • FAQ — common questions and troubleshooting