# Integration changelog

Documentation changes are separate from API versions. All endpoints here currently use /api/v1.

Canonical: https://docs-firehorsepay.powerwebhub.com/changelog
Updated: 2026-11-22; API v1

## 22 November 2026 · Developer Portal

Public documentation separated from the authenticated dashboard. Added a hosted-checkout path, task-based guides, endpoint reference, local request composer, source downloads, search and machine-readable documentation.

Documented asynchronous CREATED responses, direct-create 409 behavior, Sandbox defaults, full-refund action boundaries, provider callback history and separate amount/currency fields. Corrected Postman canonical-path and resolved-body signing.




## September 2026 · v1 documentation history

The former dashboard documentation snapshot covered the extended request, converted, provider, actual, credited and settlement values, FX metadata and amount-update classifications. These fields are now documented together in the amounts and FX guide.

This was a documentation revision within API v1, not a separate /api/v2 contract.


- [Amounts and FX reference](https://docs-firehorsepay.powerwebhub.com/guides/amounts-fx)

## July 2026 · v1 documentation history

The former dashboard snapshot described asynchronous provider initiation: creation can return CREATED, fast initiation can return PROCESSING with redirectUrl, and final outcomes arrive through webhooks or status retrieval. The current guides retain that lifecycle.

The documentation date does not change the API path. Existing merchant integrations continue to use /api/v1.


- [Asynchronous transaction creation](https://docs-firehorsepay.powerwebhub.com/api/create-transaction)
- [Merchant webhooks](https://docs-firehorsepay.powerwebhub.com/webhooks)

## Versioning and compatibility

The documentation date is not an API version. Historical documentation snapshots do not imply /api/v2 or /api/v3 endpoints. Check the actual path and response contract before upgrading an integration. Existing merchant and admin developer links continue to provide a route to these docs.


