> ## Documentation Index
> Fetch the complete documentation index at: https://polar.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# API Changelog

> Stay up to date with the latest changes introduced in our API

Polar uses date-based API versions to evolve the API without unexpectedly changing
the contract your integration depends on. Versions use the `YYYY-MM` format, such
as `2026-10`, and apply to API requests, responses, webhook payloads, and SDK types. [Read more](/docs/api-reference/current/versioning)

<Update label="2026-10">
  **This will become the Current version on October 1st.**

  * Removed the `secret` parameter when [creating](/docs/api-reference/2026-10/webhooks/create-webhook-endpoint) or [updating](/docs/api-reference/2026-10/webhooks/update-webhook-endpoint) webhook endpoints. New endpoint secrets are generated by Polar.
  * Added `member_id` and `member` to [license key responses](/docs/api-reference/2026-10/license_keys/get-license-key), identifying the seat member holding the key. Both are `null` for keys granted directly to a customer.
</Update>

<Update label="2026-04">
  ### Standard Webhooks signing

  New webhook endpoints with secrets generated by Polar on or after **September 8,
  2026 at 00:00 UTC** use signing compliant with the Standard Webhooks specification.

  Endpoints with secrets generated before this cutoff continue to use Polar's
  previous signing approach, preserving compatibility with existing integrations.
  Endpoints with user-provided secrets also retain the previous approach.
  We will continue to support this approach for as long as necessary; there is no
  required migration deadline.

  To adopt Standard Webhooks signing for an existing endpoint, **regenerate its
  secret** and update your webhook handler to use the new secret. When using a
  Standard Webhooks library directly, pass the new secret as-is, without
  Base64-encoding it first.

  See [webhook signature validation](/docs/integrate/webhooks/delivery#custom-validation)
  for details on both signing approaches.
</Update>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.