Stripe silently renames a response field. OpenAI latency spikes 3x overnight. Twilio deprecates an endpoint you depend on.
And you find out about all of this from customer complaints, not from your monitoring.
Your code does not change, but the ground beneath it shifts constantly. Depify's API Intelligence and Provider Tracker exist to solve exactly this problem.
Schema drift is the silent killer of API integrations. It happens when a provider changes their response format without a version bump, without a changelog entry, and sometimes without even knowing they did it.
A field your code depends on is no longer in the response.
A field changes from string to integer, or from object to array.
A new field that was not in the original schema now appears to be required in request bodies.
A flat field moves inside a nested object (e.g., user_name becomes user.name).
Schema drift catches changes in API responses. But many changes are announced weeks or months before they take effect.
Depify tracks announcements from 59 providers through multiple channels.
Official changelogs monitored automatically.
Deep scraping with pagination for providers that only announce via blog.
Open-source dependency release monitoring.
Incident tracking for real-time outage awareness.
| Impact Level | Description | Example |
|---|---|---|
| Breaking Change | Existing functionality will stop working | Stripe removes /v1/charges endpoint |
| Deprecation | Functionality will be removed in the future | Twilio announces SMS API v1 EOL |
| Security | Vulnerability or security-related change | Auth0 requires PKCE for all OAuth flows |
| Migration Required | New version available, old version sunset | SendGrid v2 to v3 mail API migration |
| Enhancement | New feature or improvement | Stripe adds new payment method |
For breaking changes and deprecations, Depify tells you what to do about it and by when.
BREAKING CHANGE
Microsoft: Office 365 Connectors Retirement
Impact: Breaking - All incoming webhook connectors
will stop working after the retirement date.
Action Required:
Migrate to Microsoft Workflows (Power Automate)
for incoming webhook functionality.
Deadline: April 30, 2026
Days Remaining: 38
Affected Integrations in Your Account:
- Teams Alert Channel (production)
- DevOps Notifications (staging)The countdown timer updates daily. As the deadline approaches, alert urgency escalates automatically.
Sometimes an API does not change its schema or deprecate an endpoint. It just gets slower. And slow is the same as broken when you have SLAs to meet.
Depify tracks P50, P95, and P99 latency for every provider and uses Z-score analysis to separate signal from noise.
| Z-Score | Meaning | Action |
|---|---|---|
| < 2 | Normal variation | No alert |
| 2 - 3 | Unusual | Warning alert |
| > 3 | Anomalous | Critical alert |
{
"endpoint": "api.openai.com/v1/chat/completions",
"metric": "p95_latency",
"current_value_ms": 4200,
"baseline_mean_ms": 1400,
"z_score": 10.0,
"severity": "critical",
"message": "P95 latency is 3x the historical baseline."
}Without Depify, you would have discovered the change when customers started reporting payment failures.
"Depify's provider tracker caught a Stripe field deprecation 3 weeks before it affected us. We had the migration done before the change even shipped."
Schema drift detection is included in all Depify plans. Provider tracking is available on Starter (3 providers), Pro (10 providers), and Enterprise (unlimited).
Z-score anomaly detection is available on Pro and Enterprise plans.
Detect schema drifts, track provider changes, and get action guidance with deadlines.
Start Free Trial