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

# Versioning

> What can change without warning, and what cannot.

The API is versioned in the path. Everything documented lives under `/api/v1/`.

```
https://api.dashlink.ai/api/v1/shortlinks/get_shortlinks
```

## What will not change within v1

These are a contract. Nothing in `v1` will break them:

* An endpoint's path, once documented
* A parameter's name and meaning
* A field's name and type in a response
* The `{"data": ...}` and `{"error": ...}` envelopes
* An error `code`'s meaning
* An HTTP status for a given outcome

## What can change

These may change without a new version, so write code that tolerates them:

* **New fields in responses.** Ignore fields you do not recognise rather than failing on them.
* **New optional parameters.** Existing calls keep their current behaviour.
* **New endpoints and new error codes.** Treat an unrecognised `code` as a generic failure of its HTTP status.
* **Message wording.** `message` is written for people and is reworded and translated. Branch on `code`.
* **Ordering, where you did not specify it.** Pass `sort_by` if order matters to you.

> [!WARNING]
>
> The most common way an integration breaks is strict response parsing — a schema validator set to reject unknown fields, or a deserialiser that throws on them. Adding a field is not a breaking change here.


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