Delivery Robots and Elevators: What to Test Beyond API Connectivity
A successful API response does not prove a delivery robot has completed a floor-to-floor trip. Elevator assignment, door state, entry and exit, and recovery after interruption all need joint testing with the building operator.

Confirm the integration scope
Check building authorization, served floors, elevator model and service agreement. KONE’s Service Robot API describes calls, floors and door status; its capabilities and access conditions should not be assumed for another elevator or building.
Test the complete journey
Record request, car assignment, arrival, door opening, robot entry, arrival at the destination floor and exit. Log each state and timeout separately instead of testing only an elevator call.
Include exceptions
Work with the property operator, elevator service provider and robot supplier to test network interruption, cancellation, unavailable cars, unexpected door state and blocked paths. Agree on waiting positions, human escalation and recovery.
Deploy under building rules
Peak passenger traffic, access control, fire and emergency operation can change the normal sequence. API testing does not replace elevator safety assessment. Confirm responsibilities, versions, access rights and contacts, then retest under approved conditions.
Sources and application limits
These public references provide background; use the documentation for the actual equipment and applicable local requirements:
ZHILIANHAI