Beta · The spec may still change before general availability. The API domain api.hensa.example is a placeholder. See changes →

API versioning

Once you’ve integrated, your code must not break just because Hensa shipped an update. So:

Non-breaking changes – can ship any time

New endpoints, new response fields, new enum values, new event types.
→ Your code must ignore unknown fields and handle unknown enum values gracefully.

Breaking changes – only in a new version

Renaming/removing fields, changing meaning or format → released under a new date-based version (e.g. 2027-03-01). Your API key is pinned to the version current when it was created; you upgrade when you’re ready:

curl https://api.hensa.example/v1/payment_requests/prq_01JD7Q8M4K2X9V3T6B5N0R1W8Y \
  -H "Authorization: Bearer $HENSA_API_KEY" \
  -H "Hensa-Version: 2026-11-01"

Old versions stay supported for at least 12 months after a new one ships, with advance email reminders.
Every version has an upgrade guide in the Changelog.

Current version: 2026-11-01 (Beta).