agent called a deprecated transactions endpoint that failed to return history older than 90 days

TL;DR

Deprecated endpoints keep answering but with reduced behaviour, and a silent 90-day window is a classic deprecation: the old endpoint serves recent data while the provider steers everyone to the new one. Check the provider's changelog for the deprecation notice and the replacement endpoint, migrate the agent's calls, and backfill the missing history from bank statements or the new endpoint's history range. Pin the API version in the client so the next deprecation announces itself as a version change instead of silent data loss.

agent called a deprecated transactions endpoint that failed to return history older than 90 days

Use this when

• History older than 90 days is missing while recent transactions arrive normally.
• The provider's docs mark the endpoint deprecated or describe a newer version.
• The agent's integration was built against an older API version and never migrated.

Not for this skill when

• The account or the API plan genuinely offers only 90 days of history. Then the data must come from statements, and no endpoint migration helps.
• All history including recent is missing. That is a broader auth or scope failure, not deprecation.

Steps

1. Confirm the deprecation: find the notice in the changelog and the recommended replacement endpoint and version. Verify: the migration target is stated by the provider, not guessed
2. Call the replacement endpoint for a test account and compare its history depth with the old endpoint's. Verify: the new endpoint returns the missing older history
3. Migrate the agent's transaction calls to the replacement endpoint with the API version pinned. Verify: the client declares its version explicitly
4. Backfill the missing history from the new endpoint or from bank statements, deduping on transaction id against the recent data already held. Verify: the combined history is continuous with no gap at the 90-day line
5. Reconcile the backfilled history totals per month against statements. Verify: each backfilled month ties to its statement

Variant phrasings

deprecated transactions endpoint 90 days history missing agent

The deprecation phrasing.

API version deprecated silent data loss migration

When pinning the version.

Compatibility: Versioned bank and accounting APIs with deprecated transaction endpoints.

Why it happens

Deprecation is a slow-motion breaking change. Providers keep old endpoints alive with degraded behaviour to avoid hard failures, and a degraded history window looks like a data problem rather than an integration problem, so teams debug their queries for weeks. The changelog is the source of truth, and version pinning converts future deprecations from silent degradation into explicit contract changes the team notices at upgrade time.

Edge cases / pitfalls

• Some providers gate history depth by plan tier on the new endpoint too; confirm the tier before assuming migration restores history.
• Deprecated endpoints can be removed with little notice after long deprecation; migrate on the notice, not on the removal deadline.
• Keep the old endpoint's data for overlap comparison during migration; it is the control set for the new endpoint's accuracy.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_X0BqW3yxH6bedxGAFIBo4A