Skip to main content
The Marky API uses date-based versioning, inspired by Stripe. This means the API evolves without breaking your existing integrations.

How it works

Every request returns a Marky-Version header with the API version used:
You can pin your integration to a specific version by sending the header:
If you don’t send the header, you get the latest version.

When we make changes

  • Non-breaking changes (new fields, new endpoints) are added without a version bump. Your existing code won’t break.
  • Breaking changes (removed fields, changed behavior) create a new version date. Your pinned version continues working until you’re ready to upgrade.

Current version

Best practices

  • Pin your version in production integrations to avoid surprises
  • Test against the latest version periodically to adopt improvements
  • Check the changelog for new features and deprecation notices