Adobe Marketo Engage marketing automation. The legacy developers.marketo.com is decommissioned; the canonical Swagger 2.0 specs (Lead/MAPI 129 paths, Asset 157 paths, Identity) live in AdobeDocs/marketo-apis. The Experience League current release-notes page carries forward-lookin
- "version": "2024-09-30" + "version": "2025-06-01" - POST /v1/marketo/charges + POST /v1/marketo/payments (auth scope changed)
- "version": "2024-09-30" + "version": "2025-06-01" - POST /v1/marketo/charges + POST /v1/marketo/payments (auth scope changed)
- "version": "2024-09-30" + "version": "2025-06-01" - POST /v1/marketo/charges + POST /v1/marketo/payments (auth scope changed)
- "version": "2024-09-30" + "version": "2025-06-01" - POST /v1/marketo/charges + POST /v1/marketo/payments (auth scope changed)
- "version": "2024-09-30" + "version": "2025-06-01" - POST /v1/marketo/charges + POST /v1/marketo/payments (auth scope changed)
The Adobe Marketo Engage API evolves without warning — endpoints move, parameters change, auth scopes tighten and old fields get deprecated. apik.dev watches the public Adobe Marketo Engage 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 Adobe Marketo Engage changelog by hand, you get a clean, dated record of exactly what changed — and why it matters.
Subscribe to Adobe Marketo Engage 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 Adobe Marketo Engage 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 Adobe Marketo Engage tracking goes live — full diffs, severity grading and migration summaries.