# Bitpont API Changelog | Versions & Integration Changes

Review Bitpont API revisions, SDK fixes and additive integration changes. Track compatibility and migration notes for partner applications.

Canonical: https://www.bitpont.com/developers/changelog/


## API 1.9 · Bitpont 5.72.0

Added 17 read resources for verified vaults, credit, staking, native BTC progress and Ostium. Seven new public market resources use the existing free-access budgets. Position reads require positions:read and explicit pagination. Updated the SDK declarations, OpenAPI, Postman and protocol coverage guides. Existing routes and signing permissions are unchanged.

## 5.61.0: bounded free discovery

Added no-key public market reads, shared usage budgets, a short public read cache and an explicit SDK public mode. Existing scoped partner endpoints remain protected. Public pages and crawler rules are unchanged. The existing API 1.8 contract remains additive; inspect each OpenAPI operation’s security requirements.

## API 1.8 · Bitpont 5.51.0

- New authenticated integration manifest with configured and authorized capabilities.
- New SDK readPlan iterator for all pages of planned position reads and explicit per-resource failures.
- Fixed the SDK allowlist that rejected the 500-recipient payment planner.
- Expanded the request builder to payment planning and swap quotes.
- Added a multi-page developer portal, generated Postman collection and page-level documentation downloads.Existing endpoint paths and resource identities remain unchanged. No signing or submission authority is added.

## API 1.7 · Bitpont 5.50.0

Added payment planning for up to 500 recipients, divided into preparation inputs of at most 50. Each transaction still requires fresh state and owner review.

## Earlier integration foundations

Existing releases introduced scoped resources, independent read batches, cursor pagination, transaction polling, partner workflow starters, portfolio read plans and custom ERC-20 Safe payment preparation. The current reference describes the installed contract, rather than claiming every Bitpont interface is exposed through the partner API.