apik
JOIN WAITLIST
TRACKING SHEET — 2 SOURCE(S)

Beeswax API changes

Beeswax is a bidder-as-a-service DSP (now part of Comcast/FreeWheel). Its Buzz API docs live on FreeWheel's ReadMe instance, exposing a changelog RSS (with deprecation notices) and an upcoming-changes page. The OpenAPI downloads are broken post-migration, so those two are the tra

LAST CHECKED
Jun 20, 2026
TRACKED SINCE
Jun 18, 2026
CHANGES / 90D
26
BREAKING / 90D
4
DETECTED CHANGES — MOST RECENT
  1. BREAKING Change Jun 20, 2026

    Upcoming Changes to the Buzz API

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

    budget_type not required field

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

    New docs.beeswax.com

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

    frequency_cap_type Field added

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

    New Macros

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

How to track Beeswax API changes

The Beeswax API evolves without warning — endpoints move, parameters change, auth scopes tighten and old fields get deprecated. apik.dev watches the public Beeswax 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 Beeswax changelog by hand, you get a clean, dated record of exactly what changed — and why it matters.

Get notified when the Beeswax API changes

Subscribe to Beeswax 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 Beeswax breaking changes and deprecations only, so you hear about what will actually break your integration and nothing else.

FREQUENTLY ASKED — BEESWAX
How do I track Beeswax API changes?
apik.dev tracks the Beeswax API for you. We scrape the public Beeswax API documentation on a schedule, diff every revision and grade what changed — so you never have to re-read the Beeswax changelog by hand. Subscribe once and we monitor it continuously.
How do I get notified when the Beeswax API changes?
When apik detects a Beeswax 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 Beeswax API changes does apik detect?
Endpoint changes, base-URL changes, authentication and parameter changes, schema changes and deprecations. Every Beeswax API change is categorised and severity-graded so you can triage at a glance.
How often is the Beeswax API checked for changes?
apik re-checks the public Beeswax documentation on a daily schedule. The most recent check for Beeswax 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 Beeswax tracking goes live — full diffs, severity grading and migration summaries.

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

Beeswax official docs ↗