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

# Trassets Data API: Real-Estate Data for Developers

> The Trassets Data API provides property, contract, accounting, and operations data for developers building property management integrations and analytics.

The Trassets Data API delivers structured, machine-readable real estate data to developers and data engineers. It exposes property information, rental contracts, financial bookings, fixed assets, and maintenance operations through a single REST interface so you can build dashboards, sync pipelines, and reporting tools without maintaining multiple integrations.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Make your first API call in under five minutes.
  </Card>

  <Card title="Authentication" icon="key" href="/authentication">
    How to request and use API keys.
  </Card>

  <Card title="Endpoint Types" icon="server" href="/concepts/endpoint-types">
    Category and raw endpoints explained.
  </Card>

  <Card title="API Reference Overview" icon="book-open" href="/api-reference/introduction">
    Browse the endpoint catalog and conventions.
  </Card>
</CardGroup>

## What you can access

The API is organized into data categories that match the live category tags (see `GET /catalog`):

* **Property** — Objects, the property structure tree, technical objects, and creditor service assignments.
* **Contracts** — Rental debits and diffs, service contracts, and lease/contract ends.
* **Accounting** — Chart of accounts, booking headers and positions, budgets, and account-range mappings.
* **Depreciation** — Fixed assets and their depreciation postings.
* **Operations** — Maintenance notifications, offers, orders, and capital projects.
* **Stakeholder** — Creditors, employees, owners, and tenants.

Each category exposes normalized, business-ready endpoints under `/{category}/{table}`, plus corresponding raw tables under `/raw/{table_name}` for bulk exports. See the [Data Model](/data-model/overview) section for entity relationships and real field names.