Announcements

Help us improve the Equinix Community by completing a quick survey

Discussions

Error EQ-2016101 when creating inbound and outbound shipments in sandbox

Error EQ-2016101 when creating inbound and outbound shipments in sandbox

sony-noc
Level 1

Hi all

I am testing how to create inbound and outbound orders via the API.

I am using the equinix sandbox and following https://developer.equinix.com/dev-docs/ecp/getting-started/schedule-shipments#step-4-schedule-inboun...

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 on https://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

tomas

Replies 3 3

Jantzen
Community Manager
Community Manager

@sony-noc - Thanks for the detailed post. I've reached out to a few folks internally and we'll get back to you soon. Stay tuned.

Jantzen
Community Manager
Community Manager

@sony-noc - I talked to someone a bit more familiar with this. They agreed that you've done the basic troubleshooting for a 500 error.

They suspected that it could be an intermittent error due to maintenance. If you are still experiencing the issue, they suggested that we'd need to dive deeper into your account. Since this is a public community, we'd ask that you reach out to api-support@equinix.com directly so we can keep your details private. 

Sorry we can't get you a resolution on the community this time. Please report back if there is any general information that the community might find helpful should others experience this issue.

Cheers,
Jantzen

sony-noc
Level 1

Thanks @Jantzen  I am still seeing the same problem. I will reach out api-support as suggested. Thanks again for looking at this.