apik
JOIN WAITLIST
TRACKING SHEET — 1 SOURCE(S)

Webtrends API changes

Webtrends A/B testing and conversion rate optimization platform (Webtrends Optimize). Active product with regular releases every 1-3 weeks. OTS (server-side testing) REST API v2.0 and CAPI (web client JS API). On-premises Analytics product is legacy/frozen. No RSS feeds; Intercom

LAST CHECKED
Jun 20, 2026
TRACKED SINCE
Mar 17, 2026
CHANGES / 90D
24
BREAKING / 90D
0
DETECTED CHANGES — MOST RECENT
  1. INFO Change Jun 18, 2026

    Release Notes - R21.2026 - 10 June 2026

    - "version": "2024-09-30"
    + "version": "2025-06-01"
    - POST /v1/webtrends/charges
    + POST /v1/webtrends/payments  (auth scope changed)
  2. INFO Change Mar 26, 2026

    Hotfix 2023.18 - 20 Nov 2023

    - "version": "2024-09-30"
    + "version": "2025-06-01"
    - POST /v1/webtrends/charges
    + POST /v1/webtrends/payments  (auth scope changed)
  3. INFO Change Mar 26, 2026

    Release - R.FXP23.01 - 01 Dec 2023

    - "version": "2024-09-30"
    + "version": "2025-06-01"
    - POST /v1/webtrends/charges
    + POST /v1/webtrends/payments  (auth scope changed)
  4. INFO Change Mar 26, 2026

    Release - R69 - 03 Jan 2024

    - "version": "2024-09-30"
    + "version": "2025-06-01"
    - POST /v1/webtrends/charges
    + POST /v1/webtrends/payments  (auth scope changed)
  5. INFO Change Mar 26, 2026

    Release - R70 - 09 Jan 2024

    - "version": "2024-09-30"
    + "version": "2025-06-01"
    - POST /v1/webtrends/charges
    + POST /v1/webtrends/payments  (auth scope changed)

How to track Webtrends API changes

The Webtrends API evolves without warning — endpoints move, parameters change, auth scopes tighten and old fields get deprecated. apik.dev watches the public Webtrends API documentation for you: we scrape it on a schedule, diff every revision and grade each change as breaking or informational. Instead of re-reading the Webtrends changelog by hand, you get a clean, dated record of exactly what changed — and why it matters.

Get notified when the Webtrends API changes

Subscribe to Webtrends and apik pages you by email or webhook the moment a change is detected — with the full diff, a severity grade and a short migration summary. Filter to Webtrends breaking changes and deprecations only, so you hear about what will actually break your integration and nothing else.

FREQUENTLY ASKED — WEBTRENDS
How do I track Webtrends API changes?
apik.dev tracks the Webtrends API for you. We scrape the public Webtrends API documentation on a schedule, diff every revision and grade what changed — so you never have to re-read the Webtrends changelog by hand. Subscribe once and we monitor it continuously.
How do I get notified when the Webtrends API changes?
When apik detects a Webtrends API change, you're notified by email or webhook within hours — with the full diff, a severity grade (breaking vs. informational) and a short migration summary. You can choose to be alerted on breaking changes only.
What kinds of Webtrends API changes does apik detect?
Endpoint changes, base-URL changes, authentication and parameter changes, schema changes and deprecations. Every Webtrends API change is categorised and severity-graded so you can triage at a glance.
How often is the Webtrends API checked for changes?
apik re-checks the public Webtrends documentation on a daily schedule. The most recent check for Webtrends ran on Jun 20, 2026.
FIG. — GET PAGED NEXT TIME

Don't find out from a 500.

apik is in private development. Join the waitlist and we'll email you the moment Webtrends tracking goes live — full diffs, severity grading and migration summaries.

No spam — one email when we launch. Unsubscribe anytime.

Webtrends official docs ↗