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

# Deprecation Guide

> Migration guide for the new modular Store data structure

To improve scalability and clarity, we have reorganized the Store data structure. Many top-level fields have been moved into specialized modules (`profile`, `geo`, `branding`, etc.).

While the old fields still return data for backward compatibility, they are marked as **deprecated** and will be removed in future versions of the API.

## Mapping Guide

Use the table below to update your integration to the new modular structure.

| Deprecated Field    | New Location              | Description                                 |
| :------------------ | :------------------------ | :------------------------------------------ |
| `name`              | `profile.name`            | The public name of the store.               |
| `logoURL`           | `branding.logoURL`        | The store's primary logo.                   |
| `bannerURL`         | `branding.banners.urls`   | List of banner image URLs.                  |
| `verticales`        | `profile.verticales`      | List of sectors (BIKE, CAR, etc.).          |
| `address`           | `geo.location.address`    | Full formatted address string.              |
| `lat`               | `geo.location.point.lat`  | Latitude coordinate.                        |
| `lng`               | `geo.location.point.lng`  | Longitude coordinate.                       |
| `addressComponents` | `geo.location.components` | Structured address parts (city, zip, etc.). |
| `googleRating`      | `reviews.google.rating`   | Average Google rating.                      |
| `googleReviewsNb`   | `reviews.google.total`    | Total number of Google reviews.             |
| `currency`          | `pricing.currency`        | ISO code and currency symbol.               |

## Why this change?

To provide a more intuitive and structured developer experience, we have moved away from a flat list of fields toward a **modular structure**.

As the Lokki API grows, a flat structure becomes difficult to navigate. By grouping fields into logical modules, we provide several benefits:

1. **Semantic Grouping**: Related data points are now found together. For example, all visual elements are under `branding`, while all physical location data is unified under `geo`.
2. **Feature Isolation**: Independent concepts like `pricing`, `booking` rules, and `cancellation` policies are now isolated in their own modules. This makes it easier to understand which part of the system a specific field affects.
3. **Readability**: The structure now reflects the business domains of a rental provider, making the JSON response self-documenting and easier to parse.

<Info>
  If you are starting a new integration, please use the **New Location** fields immediately.
</Info>