Developers · Changelog
Changelog
Developer-facing changes across approved Talvrin developer surfaces, with impact, timing, required action, and links to authoritative documentation.
For live service health, use Developer Status → For current API, data, authentication, and SDK behavior, the respective documentation stays authoritative.
Change Stream
What changed, where, and whether you need to act.
Registry snapshot [snapshot-id]
Verified 2026-09-23 14:32 UTC
Showing all 7 changes in this snapshot, newest first.
September 2026
18 Sep 2026
16:00 UTC
CHG-0007
[Legacy credential method] is deprecated
[Legacy credential method] is planned for retirement. New integrations should use [replacement method]. No sunset date has been announced yet.
Effective: Sunset date not yet announced
View details →15 Sep 2026
14:00 UTC
CHG-0006
New [dataset] fields in [Data API resource] responses
[Data API resource] responses now include [new fields] for [dataset]. Existing fields are unchanged.
Effective: Same as published[Data API version]
View details →11 Sep 2026
10:30 UTC
CHG-0005
[SDK package] handles [timeout condition] as documented
[SDK package] [version] corrects behavior on [timeout condition] so it matches the documented contract. Upgrade to pick up the fix.
Effective: Same as published[SDK package] [version]
View details →4 Sep 2026
15:00 UTC
CHG-0004
Pagination on [list endpoint] moves to [cursor parameter]
From the effective date, [list endpoint] pages with [cursor parameter] instead of [offset parameter]. Requests using [offset parameter] will return a validation error.
Effective: 15 Oct 2026, 00:00 UTC[API version]
View details →August 2026
28 Aug 2026
12:00 UTC
CHG-0003
[Integration] permission prompt now lists requested scopes
When connecting [integration], the permission prompt now lists each requested scope before approval. The scopes themselves are unchanged.
Effective: 1 Sep 2026, 00:00 UTC
View details →20 Aug 2026
09:00 UTC
CHG-0002
Updated guidance on credential rotation
Credential rotation guidance has been updated. Review it and rotate any credentials that match the conditions described in the Authentication docs.
Effective: Same as published
View details →12 Aug 2026
11:00 UTC
CHG-0001
Planned change to pagination on [list endpoint]
Announced an upcoming pagination change on [list endpoint]. Replaced by CHG-0004, which carries the confirmed timing and action.
Superseded by CHG-0004. Use the current guidance.
Effective: See successor[API version]
View details →[Legacy credential method] is deprecated
[Legacy credential method] is planned for retirement. New integrations should use [replacement method]. No sunset date has been announced yet.
- Published
- 18 Sep 2026, 16:00 UTC
- Effective
- Sunset date not yet announced
- Surface
- Authentication
- Lifecycle
- Published
- Record
- CHG-0007
Impact
Existing requests using [legacy credential method] keep working until an approved sunset date is published in a follow-up record.
What you need to do
- Identify services that authenticate with [legacy credential method].
- Move them to [replacement method] using the Authentication migration guide.
- Rotate and revoke the old credentials once traffic has moved.
Compatibility / lifecycle
Deprecated. Replacement: [replacement method]. Sunset: not yet announced. Lifecycle source: Authentication registry.
Developer documentation, not investment advice. Current product behavior remains governed by authoritative documentation and your entitlements.
How to Read This Changelog
Every label is set by a technical owner. None is inferred from wording.
Color reinforces meaning but never carries it alone. Every state appears as visible text.
Change type
New public developer capability or contract element. Used only when availability is real and approved.
Existing public behavior or contract changed. Impact details are required.
A defect affecting documented behavior was corrected. Does not imply current service health.
Existing implementations may fail or need migration. Requires compatibility approval.
Developer-relevant security or trust change approved for public, safe-summary disclosure.
Documentation changed. Product behavior did not.
Developer action
The technical owner explicitly confirmed no developer action.
Inspect the change. No mandatory migration is established.
A concrete action is needed by the effective time or other approved condition.
Implementations must move to a replacement version or path. Guidance is required.
Lifecycle
Current public record.
Material content was corrected. The correction note and time are visible.
A newer record replaces this guidance and links to its successor.
The record or guidance is no longer valid. Action guidance is disabled.
Changelog vs. Developer Status
A recent fix here is not proof that a service is healthy now.
The changelog records durable change. Each technical surface keeps its own truth. This page links to them and never replaces them.
Owns
Authentication
Supported methods, credential rules, scopes, rotation, and revocation.
Open Authentication →
Subscriptions & Feeds
No subscribe button until delivery is real.
Email alerts, RSS or Atom feeds, and webhooks for changes aren't available yet. Check this page, or the affected documentation, for current guidance.
Answer-First FAQ
Frequently asked, answered first.
A public, source-governed record of approved developer-facing changes across Talvrin developer surfaces. Each entry states what changed, where, when it takes effect, whether you need to act, and where the authoritative documentation lives.
Keep Building
From awareness to implementation.
Research and intelligence platform. No trade execution. No manufactured investment recommendations.