# Changelog (https://docs.chargeflow.io/docs/reference/changelog)



Chargeflow uses date-based API versioning. See [API Versioning](https://docs.chargeflow.io/docs/reference/concepts/api-versioning) for how to specify a version in your requests.

## 2025-04-01 [#2025-04-01]

**Release Date:** April 1, 2025

New endpoints and payload modifications:

* Added Alerts API (`GET /alerts`, `GET /alerts/{id}`, `POST /alerts/{id}/outcome`)
* Added Customer Communication endpoint
* Added Platform Accounts API (`POST`, `GET`, `PATCH /accounts`)
* Added Evidence-as-a-Service (`POST /evidence`, `GET /evidence`, `GET /evidence/{id}`)
* Added Platform Disputes (`POST /platform/disputes`)
* Updated Disputes API payload structure

## 2024-03-18 [#2024-03-18]

**Release Date:** March 18, 2024

Initial API release:

* Disputes API (`GET /disputes`, `GET /disputes/{id}`, `PATCH /disputes/{id}`)
* Evidence Upload (`POST /disputes/{id}/evidence`)
* Webhooks API (`GET /webhooks`, `POST /webhooks`, `DELETE /webhooks/{id}`)
* Health Check endpoints

## Next steps [#next-steps]

<Cards>
  <Card title="API Versioning" href="/docs/reference/concepts/api-versioning">
    How to pin a version and migrate when one is deprecated
  </Card>

  <Card title="API Reference" href="/docs/api/2025-04-01/get-started">
    The full endpoint reference for the current version
  </Card>

  <Card title="Quickstart" href="/docs/merchants/quickstart">
    Make your first request against the current version
  </Card>
</Cards>