Fail to get locations from Work Visit API
Hi all, this is the error I'm getting when calling /v1/orders/workvisit/locations { "errors": [ { "code": "EQX-161-500", "message": "The system had encountered an unexpected problem and we are tracking it with error code." } ], "ticketId": "201023052138751" } Any ideas?400 Error with Users_v2 API
Hello, Without making any changes to my scripting, I am now getting the following error message when attempting to POST (create a new user) to the Users_v2 API: {"errors":[{"code":"EQX-212-1208","message":"object instance has properties which are not allowed by the schema: %s","messageParams":[["companyName","contactDetails","firstName","lastName","locale","timezone","username"]]},{"code":"EQX-212-1218","message":"instance type (%s) does not match any allowed primitive type (allowed: %s)","messageParams":["OBJECT",["array"]]}],"ticketId":"220127161517021"} I am sending all the required parameters as defined in the API definition (https://developer.equinix.com/catalog/usersv2#operation/Create%20a%20user). Can someone help me interpret what this response means and why I am suddenly getting it without any changes on my end? Thank you.Issue with Shipments API
I'm currently getting a 400 response without any sort of indication of what the problem may be. Here is an example request that I am sending with some information redacted: { "ibxLocation": { "cages": [ { "cage": "AM2:1234", "accountNumber": "1234" } ], "ibx": "AM2" }, "customerReferenceNumber": null, "serviceDetails": { "estimatedDateTime": "2019-07-27T00:00:00+00:00", "shipmentDetails": { "noOfBoxes": 3, "trackingNumber": [ "123123123" ], "inboundType": "CARRIER", "description": null, "carrierName": "UPS" } }, "contacts": [ { "contactType": "NOTIFICATION", "userName": "test@test.com", "name": "First Last" }, { "contactType": "ORDERING", "userName": "test@test.com", "name": "First Last" } ] } Please let me know if you need any information so that we can resolve this issue.EQ-2016010 Error With Outbound Shipments
I am passing JSON for ordering outbound shipments. The JSON is below but its pretty much that same as my inbound JSON which is fine. The issue I am getting with the outbound order is that I am getting this error: b'[{"errorCode":"EQ-2016010","errorMessage":"One or more properties are invalid","correlationId":"105073684364570","additionalInfo":[{"property":"details.carrierTrackingNumbers","reason":"details.carrierTrackingNumbers should NOT have more than 1 items","value":["123456789", "987654321"]}]}]' My JSON: { "type": "OUTBOUND", "customerReferenceId": "x", "requestedDateTime": "2023-04-12T07:00:00.000Z", "cageId": "x", "details": { "carrier": "FEDEX", "numberOfBoxes": 2, "declaredValue": 1, "declaredValueCurrency": "USD", "carrierTrackingNumbers": [ "123456789", "987654321" ], "shipmentLabelRequired": false } } Just for reference this is my inbound which is working as expected. { "type": "INBOUND", "customerReferenceId": "x", "requestedDateTime": "2023-04-12T07:00:00.000Z", "cageId": "x", "details": { "carrier": "FEDEX", "numberOfBoxes": 2, "carrierTrackingNumbers": [ "123456789", "987654321" ], "cageDelivery": false } } Not really sure why I am getting that error, just hoping its something simple. This happens on both the sandbox and in prod.Shipping API v2 list issue
Hi, I am using the API to open inbound orders and I received a call today that the Shipping team cannot scan the tracking numbers and associate them to a ticket. It looks like the API is putting the tracking number string into a list instead of a string which is causing this, ['626467467487', '626467467454', '626467467465', '626467467476']. I have my app posting this in a string format using the catalog on the developer portal. The portal does state that the tracking numbers need to be inside brackets so could that be the reason? "carrierTrackingNumbers": [ "DHL930182000" ], That is the example from the catalog, I believe the brackets are causing the issue here with the Shipping department at the site.When creating INBOUND shipment I get 504 (gateway time-out) or 204 (No Content) instead of 201 (Created)
I use shipment v2 API in playground. URL of my request: https://playgroundapi.equinix.com/colocations/v2/orders/shipments JSON data of my request: { "type": "INBOUND", "requestedDateTime": "2023-03-02T10:45:41Z", "cageId": "1234", "details": { "carrier": "OTHER", "carrierName": "New Carrier", "numberOfBoxes": 2, "carrierTrackingNumbers": [ "t1Z294AK92654678989", "t1Z086DK96424456780" ] } } I get two possible responses for this same request: 504 gateway time-out error { "fault": { "faultstring": "Gateway Timeout", "detail": { "errorcode": "messaging.adaptors.http.flow.GatewayTimeout" } } } 204 No Content However according to API docs, I should get 201 and the order id.Z side cross-connect assets reply
[creating new thread because follow-ups on the previous thread throws up http 403] Hi, thanks for following up! What I'm trying to do here is to reconcile Equinix's view of what cross-connect assets are installed in our patch panels with what's contained in our own internal database. The aim is two-fold: 1. ensure that Equinix' DB and our DB are ~in sync and 2. to enable us to get local notifications whenever there are asset create / delete events, which can then be used to trigger other work process flows on our side,e.g. sending out to sites to bring links live. At the moment, only A side cross-connects assets are visible via the API, but A side cross-connects only make up 20% of the installed asset based in our patch panels: the other 80% are Z side cross-connects. So you can probably see that the current output from an EQX API asset search is not that useful for us, which is a real shame. We're currently handling this reconciliation by downloading Excel spreadsheets from the portal and manually running comparisons, but this is error-prone and tedious. What we'd really like is to be able to take the information contained in the Customer Portal report spreadsheets for both A side and Z side cross-connects (the Z-side tab contains the asset IDs), but without having to go to the hassle of downloading daily reports, then passing them through Excel parsing code to pull out the columns that we need. I.e. the information that we need is already available for download from the portal via API - it's just that it's in Excel Spreadsheet format rather than JSON. So: can this info be exposed via the API? This would be a real win and a major time saver.
