Versioning

When we make a backwards-incompatible change, we release a new dated version,
such as 2026-09-03.

Your token is pinned to the newest version at the time you created it. To use a
different version for one request, set the Community-Version header:

curl https://api.community.com/members \
  -H "Authorization: Bearer community_api_..." \
  -H "Community-Version: 2026-09-03"

Upgrading

1. Test your integration with the new version in the Community-Version header.
2. Create a new token. It's pinned to the newest version.
3. Switch your integration to the new token and revoke the old one.

Each version is supported for at least one year after the next one ships.

Backwards-compatible changes

These ship without a new version, so your integration must handle them:

• New endpoints.
• New optional request parameters.
• New fields in responses.
• New error codes.

Versions