API Reference

Die RoomZ API ermöglicht den Zugriff auf alle Kernfunktionen und kann für Integrationen mit Drittsystemen genutzt werden.

Basis-URL: /api/mobile/

Authentifizierung

Login

POST /api/mobile/login
Content-Type: application/json

{
  "email": "user@example.com",
  "password": "secret"
}

Response:

{
  "token": "abc123...",
  "user": {
    "id": 1,
    "name": "Max Mustermann",
    "email": "user@example.com",
    "role": {
      "id": 2,
      "name": "Geschäftsführer"
    }
  }
}

Authentifizierte Requests

Alle weiteren Requests erfordern den Token im Header:

Authorization: Bearer {token}

Logout

POST /api/mobile/logout
Authorization: Bearer {token}

Push Notifications

Token registrieren

POST /api/mobile/push/register-token
Authorization: Bearer {token}
Content-Type: application/json

{
  "token": "ExponentPushToken[...]"
}

Dashboard

KPIs abrufen

GET /api/mobile/dashboard
Authorization: Bearer {token}

Response:

{
  "open_tickets": 5,
  "active_tenants": 42,
  "overdue_payments": 1250.00,
  "monthly_income": 15000.00
}

Tickets

Liste abrufen

GET /api/mobile/tickets?status=open
Authorization: Bearer {token}

Query-Parameter:

• status: open, in_progress, closed, all
• assigned_to_me: 1 (nur eigene)

Response:

{
  "data": [
    {
      "id": 1,
      "title": "Heizung defekt",
      "description": "...",
      "priority": "high",
      "status": "open",
      "category": { "id": 1, "name": "Reparatur" },
      "location": { "id": 1, "name": "Haupthaus" },
      "room": { "id": 5, "name": "Zimmer 105" },
      "assigned_to": null,
      "created_at": "2026-02-04T10:00:00Z"
    }
  ],
  "meta": {
    "current_page": 1,
    "total": 15
  }
}

Ticket erstellen

POST /api/mobile/tickets
Authorization: Bearer {token}
Content-Type: application/json

{
  "title": "Neues Ticket",
  "description": "Beschreibung...",
  "priority": "medium",
  "category_id": 1,
  "location_id": 1,
  "room_id": 5
}

Ticket-Details

GET /api/mobile/tickets/{id}
Authorization: Bearer {token}

Ticket aktualisieren

PUT /api/mobile/tickets/{id}
Authorization: Bearer {token}
Content-Type: application/json

{
  "status": "in_progress"
}

Ticket übernehmen

POST /api/mobile/tickets/{id}/claim
Authorization: Bearer {token}

Als gelesen markieren

POST /api/mobile/tickets/{id}/mark-read
Authorization: Bearer {token}

Kommentar hinzufügen

POST /api/mobile/tickets/{id}/comments
Authorization: Bearer {token}
Content-Type: multipart/form-data

comment: "Mein Kommentar"
image: [file]

Zeiterfassung

Laufende Zeit abrufen

GET /api/mobile/time-entries/running
Authorization: Bearer {token}

Response:

{
  "id": 123,
  "activity": { "id": 1, "name": "Reinigung" },
  "started_at": "2026-02-04T08:00:00Z",
  "running_time_seconds": 3600
}

Zeit starten

POST /api/mobile/time-entries/start
Authorization: Bearer {token}
Content-Type: application/json

{
  "activity_id": 1
}

Zeit stoppen

POST /api/mobile/time-entries/stop
Authorization: Bearer {token}
Content-Type: application/json

{
  "break_minutes": 30,
  "notes": "Zimmer 101-105"
}

Monatsliste

GET /api/mobile/time-entries?month=2026-02
Authorization: Bearer {token}

Freigeben

POST /api/mobile/time-entries/{id}/approve
Authorization: Bearer {token}

Ablehnen

POST /api/mobile/time-entries/{id}/reject
Authorization: Bearer {token}
Content-Type: application/json

{
  "reason": "Pausenzeit fehlt"
}

Aktivitäten

Liste abrufen

GET /api/mobile/activities
Authorization: Bearer {token}

Response:

[
  { "id": 1, "name": "Reinigung" },
  { "id": 2, "name": "Reparatur" },
  { "id": 3, "name": "Wartung" }
]

Standorte

Liste abrufen

GET /api/mobile/locations
Authorization: Bearer {token}

Zahlungen

Liste abrufen

GET /api/mobile/payments?status=overdue
Authorization: Bearer {token}

Query-Parameter:

• status: pending, paid, overdue, all
• type: rent, parking

Als bezahlt markieren

POST /api/mobile/payments/{id}/mark-paid
Authorization: Bearer {token}
Content-Type: application/json

{
  "payment_method": "bank_transfer"
}

Als unbezahlt markieren

POST /api/mobile/payments/{id}/mark-unpaid
Authorization: Bearer {token}

Mieter

Liste abrufen

GET /api/mobile/tenants?status=active
Authorization: Bearer {token}

Details abrufen

GET /api/mobile/tenants/{id}
Authorization: Bearer {token}

Response:

{
  "id": 1,
  "first_name": "Max",
  "last_name": "Mustermann",
  "email": "max@example.com",
  "phone": "+49...",
  "room": {
    "id": 5,
    "name": "Zimmer 105",
    "floor": { "name": "1. OG" },
    "location": { "name": "Haupthaus" }
  },
  "monthly_rent": 500.00,
  "move_in_date": "2026-01-01",
  "parking_spot": { "id": 1, "name": "P001" },
  "payments": [...]
}

Benachrichtigungen

Liste abrufen

GET /api/mobile/notifications
Authorization: Bearer {token}

Als gelesen markieren

POST /api/mobile/notifications/{id}/read
Authorization: Bearer {token}

Alle als gelesen markieren

POST /api/mobile/notifications/mark-all-read
Authorization: Bearer {token}

Fehler-Responses

Status	Bedeutung
401	Nicht authentifiziert – Token fehlt oder abgelaufen
403	Keine Berechtigung für diese Aktion
404	Ressource nicht gefunden
422	Validierungsfehler – Details im errors-Feld
500	Serverfehler

Beispiel Validierungsfehler:

{
  "message": "The given data was invalid.",
  "errors": {
    "email": ["The email field is required."]
  }
}