apik
JOIN WAITLIST
TRACKING SHEET — 3 SOURCE(S)

Emarsys API changes

SAP Emarsys is an omnichannel customer-engagement platform. Signals: the published SMS Partner Service OpenAPI specs (service + callbacks, on GitHub) and the Stoplight developer-portal changelog (forward-looking API changes). The core/Suite API reference is a Stoplight SPA with n

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

    Inbound messages callback

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

    Delivery reports callback

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

    Test connection with the provided custom fields with the provider

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

    Send SMS messages to the Partner API

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

    Delete a client's configuration by their ID

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

How to track Emarsys API changes

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

Get notified when the Emarsys API changes

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

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

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

Emarsys official docs ↗