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.
​
MCP

​
MCP Server: batch lookups, smarter name search, lighter tool payload

  • Batch lookups. get_offer and get_affiliate take up to 25 ids via offer_ids / affiliate_ids; list_offers, list_affiliates and advertisers take up to 50 names, with misses under unmatched; invoice affiliate_id and cap ids accept pipe-separated sets. Each filter states whether it batches. See Limits.
  • Smarter name search. search matches the phrase, then all its terms in any order, then any term ranked by matches; a relaxed result carries match_mode.
  • Lighter tool payload. A smaller tool catalogue means fewer tokens spent before your question is read.
  • Sharper reporting controls. Delta keys such as revenue_delta sort comparison mode, wide comparisons rank the top 50 rows with a scope note, and sort_by accepts any grouped dimension, so a date series comes back chronological.
  • Consistent totals, forgiving domains. run_network_summary follows the report’s no-denominator rule for ctr; get_traffic_health_domain accepts the www. or bare form and returns resolved_domain.
  • Richer records. Offer scrub-rate settings, partner internal notes and user emails, and the article body on top help-center results.
​
MCP
  • ISP trends — list_traffic_health accepts type="isp_trends", surfacing the tracking domain x ISP pairs whose click volume is declining against every comparison day (yesterday measured against the single days 7, 14 and 30 back). Each row carries clicks, conversions and revenue with the four day snapshots plus the change and percent trend from each, so a partner reporting “my traffic dropped” can be traced to a specific ISP and domain. Traffic Health Premium; scope to one domain with domain. See Traffic Health.
  • Coupon codes by label — list_entities(type="coupon_code") accepts affiliate_label and offer_label, resolved server-side. Asking for every code held by partners carrying a label is now a single call, whatever the size of the label — no paging the partner list to collect ids and passing them back. Each intersects with its own id filter, and offer and affiliate labels are separate namespaces. See Supported entity types.
  • Coupon code timestamps — time_created and time_saved are returned in the network timezone, matching the other entity types.
  • Clearer coupon validation — an unrecognised status on coupon_code now returns an error naming the valid values instead of quietly matching nothing.
​
MCP

​
MCP Server — deeper reporting, richer records, and three new entity types

  • Scrub and view-through metrics — run_performance_report returns invalid_cv_scrub and view_through_cv in rows and totals, so the conversion family reconciles: total_conversions = conversions + invalid_cv_scrub + view_through_cv. duplicate_clicks is now returned alongside them. See run_performance_report.
  • Custom metrics in rows — each row carries a custom_metrics object keyed by your network’s custom metric names, using the engine’s formatted values.
  • Fuller event records — search_activity returns the same detail as a single-record lookup: full geo, device, user IP, referer and coupon code on clicks; event_id, event_name, currency, payout/revenue type, geo and device on conversions. See Attribution debugging.
  • Conversion identity fields — language, brand, dma, device_model, IPs, user agent, ISP, carrier and advertising IDs, carrying the same GDPR masking as the REST conversion export.
  • Conversion notes — the notes your customers add to a conversion are returned from both get_entity and search_activity.
  • Search conversions by email — both list_entities(type="conversion") and search_activity(type="conversion") accept an email filter. If a newly added filter appears to be ignored, reconnect your MCP client so it picks up the current tool definitions. See Troubleshooting.
  • Three new entity types — on_hold_conversion for the review queue, offer_cap for cap consumption network-wide with used and pct_used per cap, and reporting_adjustment for manual payout and revenue adjustments. See Supported entity types.
  • Partner payment terms — get_affiliate accepts include=billing for billing frequency, payment method, invoice type, payable and VAT settings. See get_affiliate.
  • Core offer fields — get_offer returns category_id, category_name, labels, encoded_value, session_duration and attribution_method without needing an include.
  • Clearer report validation — an unrecognised sort_by metric now returns an error naming get_report_schema rather than being ignored.
​
MCP

​
MCP Server — now available to every network

The MCP Server is generally available. Early access is over — no request, approval, or per-network enablement is required. Any network user with a valid Network API key can connect and start querying immediately. See the Overview and Quickstart.
  • No more waitlist — the previous “email support to request access” step is gone. Point your MCP client at https://mcp.eflow.team (or https://mcp-eu.eflow.team for EU-hosted accounts) and authenticate with your Network API key.
  • Agent Skills — packaged, auto-activating workflows (performance review, tracking setup, conversion scrubbing, traffic-quality audit, funnel integrity, yield and geo optimization) now run on top of the read-only MCP tools. See Agent Skills.
​
MCP

​
MCP Server — reporting trust and read-tool refinements

  • Conversions by transaction — list_entities(type="conversion", filters={"transaction_id":…}) returns all conversions for a transaction as a flat, paginated list (no date range). See Attribution debugging.
  • Creative markup — get_entity(type="creative") returns the full record including html_code; list_entities stays lean. See Supported entity types.
  • advertiser_event by offer — list_entities(type="advertiser_event") accepts offer_id in place of advertiser_id (the advertiser is resolved from the offer).
  • applied_query — run_performance_report and run_network_summary echo the resolved query (date window, timezone, currency, filters) so results are reproducible. See run_performance_report.
  • metric_glossary — both reporting tools include inline definitions for the easily-misread metrics (the conversion-counting family, event revenue, percent vs ratio).
  • Server-side totals — run_performance_report returns a totals object over the full matched set, with ratios re-derived from the sums rather than averaged — so you never sum rows yourself.
  • Capability onboarding — the server now advertises what it can do (and starter questions) to the client on connect, so “what can you help me with?” gets a grounded answer. See Quickstart.
​
APIMCP

​
Traffic Health — Network API endpoints and MCP tools

Traffic Health — the operational health of the domains and hosting IPs behind your tracking and conversion links (uptime, SSL, DNS and expiry incidents, blocklist reputation, remediation tasks, and per-domain hosting/SSL, assignment and revenue detail) — is now available through both the Network API and the MCP Server.
  • Network API — a full Traffic Health reference covering network-wide and per-domain situation, incidents, tasks, blocklist reputation, assignments, usage, and mismatches. Start with Get Traffic Health Access.
  • MCP Server — two read-only tools: list_traffic_health for network-wide rollups and get_traffic_health_domain for one domain’s full picture in a single call. See Traffic Health tools.
  • Free vs Premium — core health, tasks, hosting and SSL are available to any network with Traffic Health enabled; blocklist reputation, external domain monitoring, and per-domain assignments/usage require Traffic Health Premium. Premium-only requests return a notice instead of data rather than erroring.
​
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 metrics — run_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 defaults — run_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.
​
APIMCP

​
Sub and advertiser parameters extended from 5 to 10

Tracking now supports sub1–sub10 affiliate sub-parameters and adv1–adv10 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 SDK — EF.click(), EF.conversion(), and EF.impression() accept the new parameters
  • Webhooks & Firehose — conversion webhook and Firehose payloads carry sub1–sub10 and adv1–adv10
  • MCP Server — run_performance_report, search_activity, and the event entity types filter on the full range; see Attribution debugging, the new home for click, conversion, and transaction lookup documentation
​
MCP

​
MCP Server — transaction lookup and tool consolidation

One capability added and four tools consolidated, with no net growth in the tool list.
  • Transaction lookup — get_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.
  • Deprecations — get_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.
​
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.
​
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.
​
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
​
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