Letmc agentOS API V3, Maintenance Call Group
Browse all Letmc APIs✓ Official Vendor SpecProductivityTask ManagementapiKey, basic1 EndpointsREST
For Agents
Create a new maintenance job for a specific letmc.com agentOS branch so that property maintenance work can be raised against an existing tenancy.
Use for: I need to raise a maintenance job for a tenancy on agentOS, Create a maintenance ticket for a specific letmc branch, Submit a repair request to a letting agent's agentOS V3 system, Forward a tenant maintenance issue into agentOS
Not supported: Does not handle tenancy creation, rent collection, viewings, or maintenance job closure — use for raising new maintenance jobs into agentOS V3 only.
The agentOS Maintenance Call Group API exposes the maintenance ticket creation flow used by letting agents on the agentOS V3 platform. It lets a connected branch raise a new maintenance job for a property under management, attach the relevant tenancy and contact details, and forward it to the maintenance workflow. The API is scoped narrowly to job creation rather than full ticket lifecycle management.
Install Jentic One Beta
Connect the agentOS API V3, Maintenance Call Group to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the agentOS API V3, Maintenance Call Group, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with agentOS API V3, Maintenance Call Group API.
Raise a new maintenance job against a specific agentOS branch using its short name and branch ID
Attach contact, tenancy, and property context to a maintenance request when it is created
Authenticate branch-level requests using the ApiKey header issued to letting agents
Submit maintenance work intake from external systems into the agentOS V3 platform
Trigger downstream maintenance workflows by handing off job details to the agentOS back office
Use Cases
Patterns agents use agentOS API V3, Maintenance Call Group API for, with concrete tasks.
★ Tenant portal maintenance intake
A tenant portal collects maintenance issues from renters and forwards them into the letting agent's agentOS V3 system. Each submission is posted to /v3/maintenance/{shortName}/maintenance/{branchID}/createmaintenancejob with the branch identifier and property details so the agency back office can triage and dispatch the work. This avoids manual rekeying and gets repair requests into the property manager's queue within seconds.
Create a maintenance job at /v3/maintenance/acme/maintenance/123/createmaintenancejob with the tenant name, property reference, and a description of a leaking radiator, then confirm the job was accepted.
Smart-home device fault dispatch
A smart-home monitoring service detects a boiler or smoke alarm fault and needs to escalate to the managing agent. The agent uses the agentOS Maintenance Call Group API to open a maintenance job under the correct branch with the device context attached, so a contractor can be assigned through the agency's normal workflow.
Post a maintenance job for branch 42 of short name 'rivervalley' describing a boiler pressure fault detected by a connected sensor at flat 3B.
AI agent maintenance dispatch via Jentic
An AI agent triaging tenant emails identifies a maintenance issue and needs to file it with the managing agency. Through Jentic, the agent searches for 'create a maintenance job', loads the agentOS V3 schema, and executes the call with branch credentials held in the Jentic vault. The agent never sees the raw ApiKey value, and integration takes minutes rather than days of bespoke work.
Use Jentic to search 'create a maintenance job', load the agentOS V3 maintenance operation, and submit a job for branch 88 with a tenant-reported leak.
Key Endpoints
1 endpoints — the agentos maintenance call group api exposes the maintenance ticket creation flow used by letting agents on the agentos v3 platform.
METHOD
PATH
DESCRIPTION
POST
/v3/maintenance/{shortName}/maintenance/{branchID}/createmaintenancejob
Create a maintenance job for a specific branch.
POST
/v3/maintenance/{shortName}/maintenance/{branchID}/createmaintenancejob
Create a maintenance job for a specific branch.
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
letmc.com ApiKey and Basic credentials are stored encrypted in the Jentic MAXsystem vault. Agents receive scoped access to the createmaintenancejob operation without ever seeing the raw ApiKey header value.
Intent-based discovery
Agents search Jentic with phrases like 'raise a maintenance job for a property' and the platform returns the agentOS V3 createmaintenancejob operation with its input schema, so the agent can call it without browsing letmc.com docs.
Time to first call
Direct integration with agentOS: 1-2 days handling branch-scoped ApiKey distribution, request schema, and error retries. Through Jentic: under 30 minutes to search, load, and execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using agentOS API V3, Maintenance Call Group API through Jentic.
What authentication does the agentOS Maintenance API use?
The API supports two schemes: an ApiKey passed in the 'ApiKey' HTTP header (issued per branch) and Basic HTTP authentication. Through Jentic, these credentials are stored in the MAXsystem vault and injected at request time, so the agent never handles the raw ApiKey or basic credentials directly.
Can I create a maintenance job for any branch with the agentOS Maintenance API?
Yes, but the request must include the branch's short name and branch ID in the URL path (/v3/maintenance/{shortName}/maintenance/{branchID}/createmaintenancejob), and the supplied ApiKey must be authorised for that branch. There is one createmaintenancejob endpoint, so this API only handles job creation, not editing or closing.
What are the rate limits for the agentOS Maintenance API?
letmc.com does not publish a public rate-limit figure for the Maintenance Call Group endpoint. Treat this as a transactional intake API: batch heavy backfills outside business hours and retry with exponential backoff if you receive 429 or 503 responses.
How do I submit a maintenance job through Jentic?
Install the SDK with 'pip install jentic', then search for 'create a maintenance job' to discover the createmaintenancejob operation, load its input schema, and execute with the branch's shortName, branchID, and the maintenance details. Jentic injects the ApiKey for the branch automatically.
Does this API let me update or close maintenance jobs after they are raised?
No. The Maintenance Call Group exposes a single POST createmaintenancejob endpoint. Once a job is created it is handed off to the agentOS back office for triage, dispatch, and closure, which are managed inside agentOS rather than over this API.
GET STARTED