fegura.ai
fegura.ai
Get API Key

API Versioning

The Fegura API uses date-based versioning, similar to Stripe. This ensures your integrations remain stable while allowing us to evolve the API over time.

How Versioning Works

Every API key is pinned to a specific API version at the time of creation. Your requests will use this version by default, ensuring consistent behavior even as new versions are released.

Current Version

Latest version:2026-02-01

Specifying a Version

You can override the default version by including the Fegura-Version header in your request:

curl https://api.fegura.ai/api/accounts \
  -H "Authorization: Bearer feg_live_your_api_key" \
  -H "Fegura-Version: 2026-02-01"

Version Selection Logic

  1. Header specified: Uses the version in Fegura-Version
  2. No header: Uses the version your API key was created with

Backwards Compatibility

We commit to the following compatibility guarantees:

  • No breaking changes without a new version - Existing fields, endpoints, and behaviors remain stable within a version.
  • Additive changes are safe - New optional fields, endpoints, or enum values may be added to existing versions.
  • Deprecation warnings - Old versions will receive deprecation notices before being sunset.
  • 12-month support minimum - Each version is supported for at least 12 months after the next version is released.

What Constitutes a Breaking Change

  • Removing or renaming an endpoint
  • Removing or renaming a response field
  • Changing a field's type (e.g., string to number)
  • Changing the meaning of an existing field
  • Adding a required parameter
  • Changing error codes or response formats

Version History

VersionReleasedStatusChanges
2026-02-012026-02-01CurrentInitial API release.

Upgrading Versions

To upgrade to a new API version:

  1. Review the changelog - Check the changelog for breaking changes.
  2. Test with the header - Add the Fegura-Version header to test requests before committing.
  3. Update your integration - Modify your code to handle any changes in request or response formats.
  4. Create a new API key - Generate a new key to pin it to the new version, or continue using the header.

Response Headers

Every response includes version information:

HTTP/1.1 200 OK
Fegura-Version: 2026-02-01
Content-Type: application/json
...

This confirms which version was used to process your request, useful for debugging when the header wasn't explicitly set.