Site access, Smart Hands and shipments

Scope#

Three services cover physical work at a data center: site access for your own staff and visitors, Smart Hands for work done by Equinix staff, and shipments. Every request on this page takes effect when it is sent. None of these APIs defines a dry run, and Smart Hands is billed.

Site access#

import com.eqixiac.equinix.operations.model.OrderResponse;
import com.eqixiac.equinix.operations.model.json.creators.WorkVisitCage;
import com.eqixiac.equinix.operations.model.json.creators.WorkVisitDetails;
import com.eqixiac.equinix.operations.model.json.creators.WorkVisitOrderRequest;
import com.eqixiac.equinix.operations.model.json.creators.WorkVisitVisitor;

WorkVisitDetails visit = WorkVisitDetails.builder(
        List.of(new WorkVisitCage("DC6:01:012345").accountNumber("123456")),
        "2026-11-20T14:00:00Z",
        "2026-11-20T18:00:00Z",
        List.of(WorkVisitVisitor.nonRegistered("Dana", "Okafor", "Example Networks")))
    .openCabinet(true)
    .build();

OrderResponse order = ops.workVisits().order(
    WorkVisitOrderRequest.builder(visit)
        .description("Replace failed line card, slot 3")
        .customerReferenceId("CHG-10492")
        .build());

workVisits().listLocations() returns the IBXs, cages and cabinets the user may request access to, with the identifiers that the cage argument expects.

Smart Hands and shipments#

smartHandsRequests() has one create method per order kind: equipment install, shipment unpack, move or run jumper cable, cage escort, locate package, pictures and documentation, patch cable install and removal, cage cleanup, cable request and other. Each takes a SmartHandsRequestJson built from the IBX location, the contacts, the schedule and the service details for that kind. listTypes() and listLocations() return the valid kinds and locations.

shipments().orderInbound(...), orderOutbound(...) and orderPendingStorage(...) take typed requests for the three shipment variants. A Smart Hands or shipment order is billable, and the APIs define no dry run for either.

Worked example: colocation operations walkthrough.