eqixiacEquinix Infrastructure as Code

Data center operations

Cross connects, site access, Smart Hands, shipments, tickets, orders, billing and reports: the operational APIs of a colocation deployment.

Scope#

These APIs cover the operational side of a colocation deployment: cross connects, site access, Smart Hands, shipments, tickets, orders, billing and reports. Equinix documents each as its own product API. In the SDK they share one entry point, the Operations class, obtained with eq.operations() or new Operations(credentials). The samples call it ops. Cross Connect and Digital LOA also have product entry points on the session, eq.crossConnects() and eq.digitalLoas(), which give access to both API families of each product.

Product or functionAccessorPage
Cross Connecteq.crossConnects(): orderApi() and fabricApi() BetaCross connects and Digital LOA
Digital LOAeq.digitalLoas(): diloaApi() and fabricApi() BetaCross connects and Digital LOA
Site accessworkVisits()Site access, Smart Hands and shipments
Smart HandssmartHandsRequests()Site access, Smart Hands and shipments
Shipmentsshipments()Site access, Smart Hands and shipments
Trouble ticketstroubleTickets(), troubleTicketOrders()Orders and tickets
Orders and quotesorderHistory(), orders(), quotes(), secureCabinets()Orders and tickets
SupportsupportCases(), supportPlans()Javadoc
Billinginvoices(), billingAccounts(), billingAccountsSearch()Billing and reports
Reportsreports()Billing and reports
Assets and lookupsassets(), attachments(), lookups()Javadoc
Notificationsnotifications(), unifiedNotifications()Javadoc; push delivery through the Messaging Gateway
Facility dataIBXSmartViewIBX SmartView

Order model#

An order create returns an order number and no resource body, and the v2 order APIs define no operation that reads the ordered resource. The status of an order is read from order history. The SDK has no crossConnects().list(), troubleTickets().list() or workVisits().list().

SDK method names carry no API version. Where a function needs both a v1 and a v2 API, the client calls both, and the version appears only in the request URL.

Service behaviour observed live#

  • Attachments, finance accounts, reports and asset search return their paging block as page (Pagination).
  • Attachments answered 504 and asset search answered 500 with an empty body intermittently on 2026-11-11. The default policy retries both statuses for GET. Asset search is a POST, which the default policy does not retry on a 5xx (Retries).
  • The Digital LOA search requires a non-empty filter.and. The privateBetaAccess and betaTermsAgreement endpoints answered 404.
  • The order-history product-type enum on the live service also contains INBOUND_SHIPMENT and OUTBOUND_SHIPMENT, which the specification lacks.

Worked example: colocation operations walkthrough.