API Changes

This page covers API developments across InfraRails, Hyperhash, and Foundry.

For broader product announcements, see Platform Updates. For APIs scheduled for retirement, see Deprecations.

Latest API developments

Infrarails — API enhancements

Status: Pre-release — Deployment verification pending

Last updated: October 20, 2026

InfraRails API development has introduced several improvements to ledger management, transaction processing, authentication, and developer integration workflows.

The following changes are included in the current development implementation but should not be considered generally available until deployment and verification are complete.

Added — API key management

New operations for managing ledger API credentials.

Credential rotation invalidates the previous ledger key.

Applications must securely store newly issued credentials and update their configuration after rotation.

Added — Account lifecycle management

A new operation provides controlled account status management.

Supported account states:

• ACTIVE
• SUSPENDED
• CLOSED

Account closure requires the relevant balance and lifecycle conditions to be satisfied.

Closed accounts cannot be reactivated through this operation.

Added — Transaction lookup

A new endpoint supports transaction retrieval using an existing operation identifier.

Supported lookup parameters include:

• ledger_id
• idempotency_key
• reference

Reference-based lookup also supports pagination parameters.

This functionality helps applications investigate uncertain transaction outcomes without automatically creating a new financial operation.

Improved — Pagination and filtering

Ledger, account, and transaction listing operations have been extended with cursor-based pagination.

Affected endpoints:

Pagination parameters include:

• limit
• nextToken

Supported filters depend on the resource.

Paginated responses use a structured format:

{
  "data": [],
  "nextToken": null
}

Existing response compatibility should be verified before production rollout.

Improved — Transaction reliability

Transaction-processing improvements include:

• Atomic idempotency record creation for eligible transaction operations.
• Duplicate-operation detection.
• Conflict handling for mismatched requests using an existing idempotency key.
• Conditional transaction status updates.
• Additional validation of monetary amounts.

These improvements are intended to reduce the risk of duplicate financial postings and conflicting transaction updates.

Security — Authentication and authorization

Security improvements include:

• Stronger ledger ownership checks.
• Reduced exposure of API credentials.
• Hashed storage for newly generated ledger API keys.
• Additional credential validation.
• Enforcement of applicable ledger status requirements.
• Safer handling of unexpected application errors.

Legacy credentials may require rotation as part of the migration process.

Developer experience — OpenAPI specification

An OpenAPI 3.1 specification has been drafted for the existing InfraRails HTTP API.

The specification covers:

• Ledger management.
• API key management.
• Account management.
• Balances and statements.
• Transaction operations.
• Transaction lookup.
• Accounting entries.

The specification requires final verification against the deployed API before being treated as the authoritative public contract.

---

Upcoming API development

The following capabilities are planned and are not yet documented as released APIs.

Endpoint paths, schemas, and availability for planned capabilities will be published when their implementations are confirmed.

Breaking changes

Breaking changes may require developers to modify an existing integration.

Examples include:

• Changes to authentication requirements.
• Removal or renaming of request parameters.
• Changes to response structures.
• Modified transaction validation rules.
• Removal of deprecated endpoints.
• Changes to supported lifecycle operations.

Current breaking-change notices

No production breaking-change notice has been published on this page.

The pre-release InfraRails changes described above may affect existing development integrations, particularly credential management and paginated response handling.

API compatibility

Developers should follow the API contract for the environment and version they are using.

We recommend:

1. Reviewing API changes before upgrading an integration.
2. Testing modified workflows in an appropriate non-production environment.
3. Validating authentication and credential rotation behavior.
4. Handling documented errors and transaction statuses.
5. Preserving idempotency keys when retrying financial operations.
6. Updating integrations before any