Braze is a customer engagement platform. Its REST API has no dedicated public changelog/OpenAPI; the in-scope server-side change signal is the Braze Currents (event data-export) changelog. The mobile/web SDK changelogs are out of scope.
- "version": "2024-09-30" + "version": "2025-06-01" - POST /v1/braze/charges + POST /v1/braze/payments (auth scope changed)
- "version": "2024-09-30" + "version": "2025-06-01" - POST /v1/braze/charges + POST /v1/braze/payments (auth scope changed)
- "version": "2024-09-30" + "version": "2025-06-01" - POST /v1/braze/charges + POST /v1/braze/payments (auth scope changed)
- "version": "2024-09-30" + "version": "2025-06-01" - POST /v1/braze/charges + POST /v1/braze/payments (auth scope changed)
- "version": "2024-09-30" + "version": "2025-06-01" - POST /v1/braze/charges + POST /v1/braze/payments (auth scope changed)
The Braze API evolves without warning — endpoints move, parameters change, auth scopes tighten and old fields get deprecated. apik.dev watches the public Braze 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 Braze changelog by hand, you get a clean, dated record of exactly what changed — and why it matters.
Subscribe to Braze 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 Braze breaking changes and deprecations only, so you hear about what will actually break your integration and nothing else.
apik is in private development. Join the waitlist and we'll email you the moment Braze tracking goes live — full diffs, severity grading and migration summaries.