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

# Versioning and support

> How the API evolves, what counts as a breaking change, and how to reach the team.

## URL versioning

The major version is part of every path: `https://api.teambuilder.ge/v1/...`. A version, once published, keeps its behaviour. Breaking changes ship only in a new major version, such as `/v2`, which runs alongside the old one.

## Changes within v1

TeamBuilder ships additive changes to `/v1` continuously, without notice beyond the [changelog](/changelog). Build your client to tolerate them:

| Additive (can ship at any time) | Breaking (only in a new version) |
| - | - |
| New endpoints | Removing or renaming an endpoint, field or parameter |
| New optional query parameters and body fields | Making an optional parameter required |
| New fields in responses | Changing a field's type or meaning |
| New values in enums such as `category` or `rarity` | Removing an enum value |
| New error `code` values and sync row codes | Changing a status code for an existing condition |
| New response headers | Tightening validation of previously valid requests |

<Tip>
  Ignore response fields you do not recognise, and give every enum a fallback branch (for example, render an unknown badge `rarity` as `common`). Then additive changes never break you.
</Tip>

## Deprecation policy

When a version or endpoint is deprecated:

1. It is announced in the [changelog](/changelog) and by email to your company's technical contact.
2. It keeps working for **at least six months** after the announcement.
3. Where a replacement exists, the announcement links to a migration guide.

## Support

| You need | Contact |
| - | - |
| API keys, scopes, higher rate limits | [contact@teambuilder.ge](mailto:contact@teambuilder.ge) |
| Help with a failing request | [contact@teambuilder.ge](mailto:contact@teambuilder.ge), with the `request_id` (see [Errors](/reference/errors#contacting-support)) |
| A suspected leaked key | [contact@teambuilder.ge](mailto:contact@teambuilder.ge) at once, then [rotate](/authentication#rotating-a-key) |
| Product questions | Your TeamBuilder account contact |


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