How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Innago Maintenance API

Manage maintenance tickets

Innago Maintenance API is one of 9 APIs that Innago publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 4 JSON Schema definitions.

Tagged areas include Maintenance. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, rate-limit docs, and 4 JSON Schemas.

This API exposes 3 operations across 2 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api-my.innago.com/openapi.

3 operations 2 paths 8 schemas 1 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api-my.innago.com/openapi/v1
Authentication
HTTP Bearer, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

Innago Maintenance API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). An API key is passed in the header as x-api-key (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 3

Across 2 paths, the API surfaces 3 operations — 1 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Maintenance 3

Manage maintenance tickets

GET
/v2/maintenances
Get all maintenance tickets
listMaintenances 6 params → 200
POST
/v2/maintenances
Create a maintenance ticket
createMaintenance body → 200
PATCH
/v2/maintenances/{maintenanceUid}/status/{maintenanceStatus}
Resolve or reopen a maintenance ticket
updateMaintenanceStatus 2 params → 200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are MaintenanceTicketModel (13 properties), MaintenanceRequestModel (9 properties), PagingModel (4 properties), FileModel (2 properties). Each schema is shown below with its type and property counts.

MessageResponseModelResponse
object
2 properties
MaintenanceRequestModel
object
9 properties 3 required
MaintenanceTicketModel
object
13 properties
PagingModel
object
4 properties
FileModel
object
2 properties
CreateMaintenanceResponseModelResponse
object
2 properties
ErrorResponse
object
2 properties
MaintenanceListResponseModelResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

innago-maintenance-api-openapi.yml Raw ↑

Other APIs Innago publishes across the network.

Innago Expenses API
Innago External References API
Innago Health API
Innago Invoices API
Innago Leases API
Innago Payments API
Innago Properties API
Innago Tenants API
Where this information came from

This is an independent, third-party profile of Innago Maintenance API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.