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

# Versioning and resource structure

> URL-based versioning and folder and resource organization guidelines.

# Versioning and resource structure

## API versioning strategy

Use URL-based versioning.

Examples:

* [https://api.example.com/v1/](https://api.example.com/v1/)...
* [https://app.example.com/v1/](https://app.example.com/v1/)...

Why:

* Explicit versioning in every request
* Easier debugging, monitoring, and routing
* Cleaner folder structure
* Old versions can coexist safely

## Resource structure and folder organization

Use RESTful, hierarchical naming to reflect relationships.

Example:

```http theme={null}
GET /users/{user_uuid}/addresses
```

Guidelines:

* Plural nouns only (/users, /addresses)
* Keep nesting shallow (2 levels max)
* Actions are defined by HTTP verbs, not URLs