apik
JOIN WAITLIST
TRACKING SHEET — 1 SOURCE(S)

Cxense API changes

Cxense (DMP / Insight / Content APIs) was acquired by Piano; its documentation now lives on docs.piano.io. The sitewide docs RSS feed is the one actively-updated public change signal. No public OpenAPI spec or llms.txt is published.

LAST CHECKED
Jun 20, 2026
TRACKED SINCE
Jun 19, 2026
CHANGES / 90D
10
BREAKING / 90D
2
DETECTED CHANGES — MOST RECENT
  1. INFO Change Jun 20, 2026

    Conversion Types

    - "version": "2024-09-30"
+ "version": "2025-06-01"
- POST /v1/cxense/charges
+ POST /v1/cxense/payments  (auth scope changed)
    🔒 Full diffs at launch — join the waitlist
  2. INFO Change Jun 20, 2026

    Predefined values for “options_link”

    - "version": "2024-09-30"
+ "version": "2025-06-01"
- POST /v1/cxense/charges
+ POST /v1/cxense/payments  (auth scope changed)
    🔒 Full diffs at launch — join the waitlist
  3. BREAKING Change Jun 20, 2026

    Creating and updating custom field keys via API: /publisher/customField

    - "version": "2024-09-30"
+ "version": "2025-06-01"
- POST /v1/cxense/charges
+ POST /v1/cxense/payments  (auth scope changed)
    🔒 Full diffs at launch — join the waitlist
  4. INFO Change Jun 20, 2026

    Identity Linking in Piano Audience

    - "version": "2024-09-30"
+ "version": "2025-06-01"
- POST /v1/cxense/charges
+ POST /v1/cxense/payments  (auth scope changed)
    🔒 Full diffs at launch — join the waitlist
  5. INFO Change Jun 20, 2026

    Status values of the UserSubscription object

    - "version": "2024-09-30"
+ "version": "2025-06-01"
- POST /v1/cxense/charges
+ POST /v1/cxense/payments  (auth scope changed)
    🔒 Full diffs at launch — join the waitlist

How to track Cxense API changes

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

Get notified when the Cxense API changes

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

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

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

Cxense official docs ↗