LiteLog

Use this to create one property (site, building) with its settings, grouped as address, location, modules, time_tracking, verification, signature, patrols, incidents and shift_defaults; omitted groups take the company defaults. Pass the same idempotency_key (a UUID) when repeating a call. May notify people according to the company's automation rules.

create_property

Use this to create 1 to 20 properties in one call, each in the shape of create_property with a required, unique idempotency_key. All entries are checked first; if one is invalid nothing is created. Then each entry is created on its own and answered per row. May notify people according to the company's automation rules.

create_properties

Use this to plan exactly one shift at a property, optionally with the people who work it (see list_people). Times are ISO 8601 with offset. Double bookings, absences and working-time rules are checked and reported, not blocked. Pass the same idempotency_key (a UUID) when repeating a call. May notify people according to the company's automation rules.

create_shift

Use this to create a task. Get property_id from list_properties and state_id from list_task_states; due_date is YYYY-MM-DD, due_time HH:mm. Pass the same idempotency_key (a UUID) when repeating a call, so no second task is created. May notify people according to the company's automation rules.

create_task

Use this to turn an incident report into a task (incident_id from list_incidents). One task per report: a repeated call returns the existing task with created false. Title, text and priority default to the report. May notify people according to the company's automation rules.

create_task_from_incident

Use this to record a finished working time for a person at a property, e.g. a forgotten clock-out. Needs a reason; at most 45 days back and 24 hours long. Overlaps and blocked times are refused, never overridden. May notify people according to the company's automation rules.

create_time_entry

Use this after list_workflow_runs to see where one run delivered: channel (email, sms, call, push, in_app), masked recipient (j***@firma.de, +49 *** ** 12), status and time. Never the plain recipient or error text.

get_workflow_run

Use this to see which control points were scanned on which day and which were missed, per property. from and to are YYYY-MM-DD, at most 14 days. Returns scan counts per point and totals for the range.

get_checkpoint_coverage

Use this to see how each property is staffed right now: people present, running shifts, the staffing target and whether it is met. Returns numbers only, no names; use list_shifts for the people planned.

get_occupancy

Use this after list_form_responses to read the answers of one filled-in form or checklist, as label and value per field. Photos and signatures are not included.

get_form_response

Use this to read one form template with all its fields and settings. The fields have the shape create_form_template takes, so a template can serve as a model for a new draft.

get_form_template

Use this after list_incidents to read one incident report: text, status, category, severity, property, time, source and the task created from it.

get_incident

Use this to read the vacation days left and the working-time account balance of the connected account itself — never of another person.

get_my_balances

Use this after list_routes to read one patrol route: its schedules (first day, time, duration, repetition, weekdays) and its control points in walking order with the duty flag.

get_route

Use this after list_patrols to read one patrol run with its events in order (start, scans of control points, end). Returns at most 200 events.

get_patrol

Use this for "how are we doing": per property a traffic light (green, yellow, red) with shifts, hours, punctuality, incidents, patrols, missed shifts and patrols for the last 7, 30 or 90 days, each with the previous period, plus totals.

get_performance_overview

Use this to compare planned shift hours, recorded working hours and contract hours per person for a period of at most 62 days (YYYY-MM-DD, end day included), e.g. before payroll. Sorted by name.

get_target_actual

Use this after list_properties to read one property in full: address, position, modules, time tracking, verification, signature, patrol and shift settings, in the same shape create_property and update_property take. Responsible people appear only when this connection may see them.

get_property

Use this after request_export to check a report. Returns the status and, when ready, download_url: a link that works without login and expires after 60 minutes (a new link is issued when little time is left). Call again while queued or running.

get_export_run

Use this to answer "are we keeping our promises": per property the verdict of the current period (onTrack, atRisk, missed, na) and each promise with target and measured value. Worst properties first.

get_service_level_status

Use this after list_shifts to see who of the planned people checked in and out of one shift and who is missing, with the timing verdicts.

get_shift_attendance

Use this after get_task to read what happened on one task: the comments (including internal notes of the team) and the history of changes, each with time and person. Returns no attachments.

get_task_activity

Use this after list_tasks to read one task in full: description, status, property, due date, the people assigned, the repetition rule in words and, for a cleaning task of a booking, arrival and departure.

get_task

Use this after list_time_entries to read one recorded working time with its timeline (check-in, pauses, check-out and how punctual each step was).

get_time_entry

Use this to read the vacation days left and the working-time account balance of up to 25 people at once (ids from list_people). Needs the right to see the times of others; for your own account use get_my_balances.

get_person_balances

Use this after list_work_orders to read one work order: description, customer, property, positions (services and material) and the staffing demand. With include_actuals also the recorded service minutes and consumed material.

get_work_order

Use this to copy a ready-made template of the LiteLog catalogue (see list_form_catalog) into the company. It is saved as a draft; a person publishes it in the LiteLog portal. A template with the same name is not imported twice.

import_form_template_from_catalog

Use this to see who is absent in a period, for planning. Dates are calendar days (YYYY-MM-DD); an absence matches when it overlaps the period. Returns person, first day, last day and status — never the reason of an absence.

list_absences

Use this to see which automation rules (notifications, escalations) exist: name, trigger, active or not, origin and how many runs failed. Recipients and the rule graph are not included.

list_workflow_rules

Use this to see what the automation did, newest first: which rule ran when, with which status (e.g. failed) and how many attempts. Filter by rule, status or day. Error texts are not included.

list_workflow_runs

Use this to read the stays at holiday properties: arrival and departure with times, guests, booking channel and the cleaning task of the departure. Default: today plus 60 days, at most 92 days. Returns no guest names.

list_bookings

Use this to see requests of the change approval (archive, restore, correction, configuration): what is requested, by whom, why and which fields would change. Default: pending. Approving stays in the portal.

list_change_requests

Use this to see who changed which settings when (properties, roles, rules, templates, schedules …), newest first: the changed field names, not the values. With property_id only changes of that property.

list_config_changes

Use this to read the control points (scan points) of the properties. Returns name, type, property, area, the last scan and the number of scans in the last 30 days per point.

list_control_points

Use this to find customers and their customer_id, optionally by name part. Returns name, customer number and the properties assigned to each customer — no contact data.

list_customers

Use this to see which forms and checklists were filled in, newest first. Returns form template, property, status, whether a defect was reported and the time of submission — not the answers.

list_form_responses

Use this to see the ready-made form templates LiteLog offers for import (import_form_template_from_catalog). Returns catalog_key, industry, name, description and number of fields.

list_form_catalog

Use this to see the form and checklist templates of the company, sorted by name. Returns name, status (draft, active, archived), properties and number of fields — use get_form_template for the fields.

list_form_templates

Use this to find the category_id for list_incidents and set_incident_category. Returns the categories of the company for incident reports with name and description.

list_incident_categories

Use this to read incident reports (defects, damage, observations), newest first; filter by status to find open ones. Dates are YYYY-MM-DD, read as UTC days, the end day included. Returns the report text, status, category, severity, property and time.

list_incidents