Error EQ-2016101 when creating inbound and outbound shipments in sandbox
Hi all I am testing how to create inbound and outbound orders via the API. I am using the equinix sandbox and followinghttps://developer.equinix.com/dev-docs/ecp/getting-started/schedule-shipments#step-4-schedule-inbound-shipment I am able to get a token, list users, list sites, etc. When I try to create an inbound shipment, I have the following $ curl -X POST "https://sandboxapi.equinix.com/colocations/v2/orders/shipments" -H "content-type: application/json" -H "authorization: Bearer TOKEN" -d @equinix-inbound.json -v < HTTP/1.1 500 Internal Server Error < Content-Length: 187 < Content-Type: application/json; charset=utf-8 < ETag: W/"bb-fFnLakTrYhk69LoXetj3crBTst4" < x-powered-by: Express < x-apigee-message-id: 79ff47bf-5867-4677-bf9c-02c3631e25ac < x-request-id: 79ff47bf-5867-4677-bf9c-02c3631e25ac < x-apigee-dp-color: 174 < x-apigee-region: us-west1 < x-apigee-organization: eqx-apg-prod < x-apigee-environment: extsbx < x-apigee-proxy: /organizations/eqx-apg-prod/environments/extsbx/apiproxies/uecp_colocations/revisions/2 < x-apigee-proxy-basepath: /colocations/v2/orders < x-apigee-fault-flag: false < x-apigee-fault-source: target < x-apigee-fault-code: messaging.adaptors.http.flow.ErrorResponseCode < x-apigee-fault-policy: null/null < x-apigee-fault-revision: /organizations/eqx-apg-prod/environments/extsbx/apiproxies/uecp_colocations/revisions/2 < x-apigee-target-latency: 3534 < x-envoy-upstream-service-time: 3566 < Server: istio-envoy < Date: Wed, 06 Mar 2024 13:34:33 GMT < Connection: close < Set-Cookie: ADRUM_BT=R:0|g:411f30ae-de4c-44c5-9117-45f0db7d858c211|h:e; Path=/; Expires=Wed, 06 Mar 2024 13:35:03 GMT < * Closing connection [{"errorCode":"EQ-2016101","errorMessage":"The server has encountered an unexpected error. We apologize for the inconvenience. Please try again later.","correlationId":"240306133433819"}]% This is the data I am providing: $ cat equinix-inbound.json { "type": "INBOUND", "requestedDateTime": "2024-03-25T10:00:00Z", "cageId": "AM8:13:99XTM", "customerReferenceId": "My Ticket", "description": "faulty optics", "details": { "carrier": "DHL", "numberOfBoxes": 1, "carrierTrackingNumbers": [ "t1Z086DK96424456780" ] } } Based onhttps://developer.equinix.com/dev-docs/ecp/error-handling/500, I need to try later, waited a couple of hours, and same issue (with new token) I have the same issue when creating outbound shipments. $ curl -X POST "https://sandboxapi.equinix.com/colocations/v2/orders/shipments" -H "content-type: application/json" -H "authorization: Bearer CQY4dFMZoyvHTCAiRoM4hKFCokiy" -d @equinix-outbound.json -v < HTTP/1.1 500 Internal Server Error < Content-Length: 187 < Content-Type: application/json; charset=utf-8 < ETag: W/"bb-6B1fQindU9GqFhXPA+40k7P7Tk0" < x-powered-by: Express < x-apigee-message-id: 35843f21-4e43-43dc-bcfc-20f62aea8141 < x-request-id: 35843f21-4e43-43dc-bcfc-20f62aea8141 < x-apigee-dp-color: 174 < x-apigee-region: us-west1 < x-apigee-organization: eqx-apg-prod < x-apigee-environment: extsbx < x-apigee-proxy: /organizations/eqx-apg-prod/environments/extsbx/apiproxies/uecp_colocations/revisions/2 < x-apigee-proxy-basepath: /colocations/v2/orders < x-apigee-fault-flag: false < x-apigee-fault-source: target < x-apigee-fault-code: messaging.adaptors.http.flow.ErrorResponseCode < x-apigee-fault-policy: null/null < x-apigee-fault-revision: /organizations/eqx-apg-prod/environments/extsbx/apiproxies/uecp_colocations/revisions/2 < x-apigee-target-latency: 2158 < x-envoy-upstream-service-time: 2191 < Server: istio-envoy < Date: Wed, 06 Mar 2024 13:36:33 GMT < Connection: close < Set-Cookie: ADRUM_BT=R:0|g:46d6f9be-1158-4cf6-b24a-8eeb3140433d214|h:e; Path=/; Expires=Wed, 06 Mar 2024 13:37:03 GMT < * Closing connection [{"errorCode":"EQ-2016101","errorMessage":"The server has encountered an unexpected error. We apologize for the inconvenience. Please try again later.","correlationId":"240306133633192"}]% And this is the data file: cat equinix-outbound.json { "type": "OUTBOUND", "requestedDateTime": "2024-03-25T10:00:00Z", "cageId": "AM8:13:99XTM", "customerReferenceId": "My Ticket", "description": "Faulty optics", "details": { "carrier": "DHL", "numberOfBoxes": 1, "declaredValue": 1000, "shipmentLabelRequired": false, "carrierTrackingNumbers": [ "t1Z086DK96424456780" ] } } Does the sandbox support these type of queries? The cage id I use in my test is a real one. Regards tomasSolved1.9KViews0likes3CommentsError 503 Shipments v1 Pending Storage
Recently I have been having issues with the Shipments v1 endpoint for pending storage (https://api.equinix.com/v1/orders/shipment/pendingStorage), receiving 503 service unavailable. Searching the catalog, there is no 503 defined so not entirely sure what this error is stating. Looking to see if this is a bug or if the endpoint was deprecated without notice. Thank youSolved1.9KViews0likes3CommentsWork Visit API - issue EQX-161-403
Hey there, I need help! I tried to use API and create a POST REST API request to raise a Work Visit request to Equinix. but unfortunately returned the EQX-161-403 errors. Please kindly help, no idea what this error message means and how to fix this error. Here's the error message frommy PowerShell script: $workvisit = invoke-restmethod -uri "https://api.equinix.com/v1/orders/workvisit" -method POST -Headers $postParams -body $postParamsWVJson -ContentType "application/json" invoke-restmethod : {"errors":[{"code":"EQX-161-403","message":"Contacts (with userName) should be Active and Approved"}],"ticketId":"201030030XXXXXX"} Here's my PowerShell script: $postParams = @{} $postParams.Authorization="Bearer " + $token.access_token $location = invoke-restmethod -uri "https://api.equinix.com/v1/orders/workvisit/locations" -method GET -Headers $postParams -ContentType "application/json" $location2= invoke-restmethod -uri "https://api.equinix.com/v1/retrieve-orders/locations" -method GET -Headers $postParams -ContentType "application/json" $postParamsWV = ` @{"contacts" = @( @{"contactType"="ORDERING"; "userName" = "XXXX@YYY.com"}; @{"contactType"="NOTIFICATION"; "userName" = "XXXX@YYY.com"}; ); "ibxLocation"= @{"ibx" = "SAMPLE"; "cages"= @( @{"cage"="SAMPLE:00:000000"; "accountNumber" = "SAMPLE NUMBER"} )}; "serviceDetails" = @{schedule = @{startDateTime = "2020-05-10T01:00:00Z"; endDateTime = "2020-05-11T02:00:00Z" }; "visitors" =@(@{"firstName" = "John"; "lastName" = "Doe"; "company" = "NN Test"; "email" = "John.Doe@Test.com"; "mobilePhoneCountryCode" = "+81"; "mobilePhone" = "80-1111-2222";}; @{ "userName" = "DDDD@yahoo.com"} ); escortRequired = $false; openCabinet = $false; } } $postParamsWVJson = $postParamsWV|convertto-json -depth 100 $workvisit = invoke-restmethod -uri "https://api.equinix.com/v1/orders/workvisit" -method POST -Headers $postParams -body $postParamsWVJson -ContentType "application/json" Regards, AlanSolved1.8KViews0likes1CommentNew WorkVisit validation error
We have been using the API /catalog/workvisitv1for a while now and we now have a new validation error that is causing a failure to use the API endpoint: { "error": "Unable to create access request with Equinix. Status code = 400, error = {\"errors\":[{\"code\":\"EQX-161-6119\",\"fields\":[\"\\/attachments\"],\"message\":\"Justification form is mandatory for visiting the IBX : %s. Justification is available to download as part of work visit page in Equinix Customer Portal.\",\"messageParams\":[\"CH3\"]}],\"ticketId\":\"redacted\"}" } This appears to be a new validation error. I haven't seen anything regarding changes to the published API. Do you guys know if this is a bug or a new requirement?1.8KViews0likes1CommentSmart Hands ticket api
Hello guys, I am new in using curl and I have a qeustion. How it looks the final example autharization form + get smart hands type. curl -XPOST 'https://api.equinix.com/oauth2/v1/token' -H "content-type: application/json" -d '{ "grant_type": "client_credentials", "client_id": "ABCDE12345", "client_secret": "FGHIJ67890" }' and curl -X GET "https://api.equinix.com/v1/orders/smarthands/types" -H "content-type: application/json" -H "authorization: Bearer qwErtYxxxxxxxcdefGHI" I don't understand how to combine these two example in one and why I have to use second time -H "authorization: Bearer qwErtY8zyW1abcdefGHI"Solved1.9KViews0likes1CommentUnexpected problem
Hi, I'm receiving "The system had encountered an unexpected problem and we are tracking it with error code." error when attempting to post work visits or retrieve location details. I'm using correct credentials and the correct bearer token but there seems to be an issue with any request I make to the sandbox API. https://sandboxapi.equinix.com/v1/orders/workvisit/locations?detail=true { "serviceDetails": { "schedule": { "endDateTime": "2020-01-20T15:54:04+00:00", "startDateTime": "2020-01-20T14:54:04+00:00" }, "visitors": [ { "company": "xxxxxxx", "firstName": "[Test]NTTS01", "lastName": "[Test]NTTS01" }, { "lastName": "person", "firstName": "A", "company": "A corp" } ] }, "contacts": [ { "contactType": "NOTIFICATION", "userName": "xxxxxxxx" }, { "contactType": "ORDERING", "userName": "xxxxxxx" } ], "ibxLocation": { "ibx": "LD4", "cages": [ { "cabinets": [ "0000" ], "accountNumber": "xxxxxxx", "cage": "LD4:01:001S14" } ] }, "customerReferenceNumber": "xxxxxxx" } Can anyone help me !Solved1.9KViews0likes1CommentIssue 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.3.9KViews0likes5CommentsIssues with Work Visit API
Hi Mohit, I have successfully accessed my sandbox and have been attempting to send some workvisit requests. Needless to say I am experiencing a number of issues. Mostly I can get around these but there’s an odd one I am blocked with. Maybe you can help me to work out what might be the issue ? Received an error : { "errors": [ { "code": "EQX-161-403", "message": "Insufficient permission to access the resource or invoke the request." } ], "ticketId": "190801140754602" } I’m not sure what this error means but I definitely is preventing me from receiving any sensible responses. Are you able to assist? Best regards,Solved1.9KViews0likes1CommentCould you let me know how to get Cage and Cabinet list via API?
Hello I am trying to get Cage and Cabinet list via API but it returns empty results Could you advise how to get the details? Input: curl --request POST \ --url 'https://api.equinix.com/v1/assets/search?sorts=IBX&source=CAGE&exactMatch=false&offset=0&limit=100' \ --header 'accept: application/json' \ --header 'authorization: Bearer xxxxxxx' \ --header 'content-type: application/json' \ --data '{"filter":{"ibxs":["SV2"]}}' Response: { "data": [], "page": { "limit": 90, "offset": 38491869, "total": 0, "sorts": [ "IBX" ] }, "_links": { "next": { "href": "/assets/search?exactMatch=false&offset=38491869&limit=90&source=CABINET&sorts=IBX" }, "previous": { "href": "/assets/search?exactMatch=false&offset=38491869&limit=90&source=CABINET&sorts=IBX" }, "self": { "href": "/assets/search?exactMatch=false&offset=38491869&limit=90&source=CABINET&sorts=IBX" } } }2KViews0likes1CommentZ side cross-connect assets
How do you query what Z-side cross-connects are installed? The /v1/assets/search URI only provides A-side cross-connects and if you attempt to post a query for /v1/assets/{assetNumber} where assetNumber refers to a Z side crossconnect, the API returns: { "errors": [ { "code": "EQX-434-4404", "message": "No Asset found for the Id:4-xxxxxxxxxxxx" } ] } Running searches / queries for A side cross-connects works fine.2KViews0likes1Comment