Always know what changed.
A running changelog of the API, SDK and CLI - what shipped, what is deprecated and what is next. Versioning is predictable and deprecations come with notice, so upgrades never catch you off guard.
Recent releases.
The latest across the platform, SDK and tooling.
Async pagination iterators
List methods now return async iterators that walk the cursor in meta for you. Webhook signature verification helper added. Fully backward compatible - a minor bump.
View on npmIdempotency on all writes
Every create endpoint now accepts an idempotency key, making retries safe across escrow and payout calls. New reputation.updated webhook event shipped alongside.
JSON output everywhere
Added --json to every command for clean pipeline output, plus named profiles for switching between test and live accounts.
How we version.
Predictable rules so you always know what an upgrade means.
API in the path
The REST API is versioned at /api/v2. Breaking changes ship as a new version - the old one keeps working.
Semver for libraries
The SDK and CLI follow semantic versioning. Major means breaking, minor means additive, patch means fixes.
Deprecation notice
Anything being retired is marked deprecated first, with a documented timeline before removal.
Additive by default
We add fields and events without breaking existing ones - new keys in data and meta are safe to ignore.
Documented migrations
Every breaking change ships with a migration guide so the upgrade path is always written down.
Contract-tested
The {ok,data,meta} envelope is guarded by contract tests, so the API and SDK never drift apart.
Why this matters for your build.
Stability you can plan around.
No silent breaks
Your integration keeps working. Breaking changes are opt-in via a new version, never pushed under you.
Plan upgrades
Deprecation timelines let you schedule migrations on your terms, not in a fire drill.
Full transparency
Every change is on the changelog - know exactly what moved before you debug a surprise.
New power, fast
Additive releases mean fresh capabilities land often without forcing a rewrite.
Stay up to date.
Watch this page
The changelog is the source of truth for what shipped across the API, SDK and CLI.
Pin and bump deliberately
Pin SDK and CLI versions in your project, then upgrade on minor and major bumps when you are ready.
Subscribe to events
Use webhooks and release notes to hear about new events and deprecations as they land.
Release questions.
How will I know about a breaking change?
It ships as a new API version or a major SDK and CLI bump, is listed on this changelog, and comes with a migration guide. The previous version keeps running during the transition.
What is your deprecation policy?
Anything being removed is marked deprecated first and given a documented timeline before it goes away, so you have a clear window to migrate.
Are new fields safe?
Yes. We add fields to data and meta and add new webhook events without breaking existing ones. Ignore keys you do not use and your integration stays stable.
Where do I report an issue with a release?
Reach out through support or the developer channels. The SDK and CLI are versioned, so referencing the exact version helps us reproduce fast.
Build on a moving, stable platform.
New capabilities ship often, breaking changes never sneak up - start building with confidence.