Skip to content
English - United Kingdom
  • There are no suggestions because the search field is empty.

How does the legacy V3 Maintenance API work?

The V3 Maintenance API is a legacy single-endpoint API for creating maintenance jobs with manual property and tenant data entry. New integrations should use the V4 Maintenance API instead. The endpoint is at https://live-api.letmc.com/v3/maintenance/.

⚠️ Legacy API — existing integrations only. The V3 Maintenance API will not receive new features. For new integrations, use the V4 Maintenance API, which provides property and contact linking, comprehensive job management, and modern API patterns.

Key limitations

  • Single endpoint only — job creation only, no retrieval or updates
  • Property address and tenant details must be entered manually — no linking to existing records
  • External job identifier limited to 10 characters and must be unique
  • Document attachments require publicly accessible URLs (no direct upload)
  • No deduplication — each submission creates a new record

Creating a maintenance job

POST /v3/maintenance/{shortName}/maintenance/{branchID}/createmaintenancejob

Required fields:

  • ExternalID — unique identifier, maximum 10 characters
  • ReportedAt — DateTime when the issue was reported (required, cannot be default DateTime)
  • IssueTitle — summary of the maintenance issue (required)
  • TenantPhonePrimary — primary phone number (required, must pass format validation)

Optional fields:

  • IssueFault, IssueNotes — additional fault description and notes
  • IssuePriority — Low, Medium, High, or Emergency (defaults to Low if invalid value provided)
  • TenantPhoneSecondary — validated if provided
  • TenantPresenceRequested — boolean, whether the tenant needs to be present

Property information (manual entry):

  • PropertyAddress1 through PropertyAddress4
  • PropertyPostcode
  • PropertyCountry

Tenant information (manual entry):

  • TenantTitle, TenantForename, TenantSurname
  • TenantEMailAddress

Document attachments: Attach documents using the MaintenanceDocumentModel[] array:

  • MimeType — e.g. application/pdf, image/jpeg
  • URL — must be a publicly accessible URL

Validation errors

  • ExternalID must be non-empty, under 10 characters, and unique
  • ReportedAt must not be a default DateTime value
  • IssueTitle must be non-empty
  • Primary phone must pass format validation

Migrating to V4 Maintenance

The V4 Maintenance API offers: property and contact linking (no manual entry), full job lifecycle management, contractor assignment, direct document upload, no external ID length limits, and active feature development.

Test with Swagger: Select "V3.Maintenance" from the tier dropdown. Use unique External IDs when testing, and ensure any document URLs are publicly accessible.