// api changelog

SaaS API changelog and breaking change tracker

We run production integrations on these 20 APIs, so we check every one of them daily: the vendor's changelog, and where they publish one, the OpenAPI spec. This is what that monitoring has found, deduplicated and dated. Free to read, no sign-up.

In short

In the last 90 days: 40 breaking changes and 24 deprecations across 12 APIs.

Monitored APIs

API Breaking (90 d) Deprecations (90 d) Latest breaking change or deprecation Last checked
Airtable 0 0 None in 90 days
Brevo 3 0 Loyalty transaction status renamed
DATEV 0 0 None in 90 days
Discord 6 1 Custom Status Hidden by Profile Privacy Settings
Google Sheets 0 0 None in 90 days
HubSpot 8 2 Legacy APIs and Apps
Jira Cloud 2 11 Deprecation of legacy Jira dashboard Forge modules
lexoffice 0 0 None in 90 days
Linear 3 0 Removed emoji support in labels
Monday.com 0 0 None in 90 days
Notion 1 0 Notion app links domain change to notion.com
Personio 0 3 Deprecated
Pinterest API 2 1 Automatic UTM parameters for ads
Pipedrive 2 0 API v1 endpoints now out of support
Salesforce 0 0 None in 90 days
Shopify 9 2 automaticDiscounts query is removed in API version 2027-01
Slack 4 2 Assistant messaging experience (assistant_view) deprecation
Stripe 0 0 None in 90 days
Xentral 0 0 None in 90 days
Zendesk 0 2 Templating API v1-v3 end-of-life

Breaking changes this month

  1. Deprecated

  2. Deprecated

  3. Deprecation of legacy Jira dashboard Forge modules

  4. automaticDiscounts query is removed in API version 2027-01

  5. Custom Status Hidden by Profile Privacy Settings

All breaking changes of the last 30 days →

Frequently asked questions

What does this page track?
Changes to the public APIs of SaaS products we integrate: new endpoints and fields, deprecations, and breaking changes that stop existing integrations from working. Each entry links back to the vendor's own changelog.
How are changes detected?
Once a day we render each vendor's changelog page, extract its entries and classify them as breaking, deprecation, new feature, bug fix or other. Where a vendor publishes an OpenAPI spec, we also diff it against the previous day's with oasdiff, which catches changes the changelog does not mention.
How reliable are the labels?
The classification is automated, so treat a label as a pointer, not a verdict: read the vendor's note before you plan work around it. Spec diffs are exact, but a spec change is not always a behaviour change.
Can I get notified?
Yes. Every API has its own RSS feed, and there is one feed for breaking changes and deprecations across all of them. If you want someone to act on the changes rather than just read about them, that is what our managed integrations do.
Can you monitor another API?
We add the APIs our customers' integrations depend on. If you run an integration on an API that is not listed, tell us about it below.
// scoping request

We watch these APIs because we run integrations on them. If yours depend on one, we can take them over: build them properly, operate them, and handle upstream changes before your data is affected. Fixed-price scoping quote within 48 hours.

We reply within one working day. No newsletter, no sales sequence.