API X ETA - is it available?

1

Hello!

I just got an email from Ordoro with the following subject: “Estimated Delivery Date Has Arrived”.
Is the Estimated Delivery Date available somehow via API call?
I just tried @api.ordoro.com/order/<ORDER_NUMBER>/ and could not find it.

Thanks,

2

Hi,

This has already been available via the API on an Order’s rate response as
estimated_delivery_date. When you request a rate on an order, we will return the estimated delivery date as given by the carrier.

3

Hey Sophie, thanks for your prompt reply. How do I request a rate to an order via API?
I see it is possible to post something like
apiverson.ordoro.com/order/<>ORDER_NUMBER/rate/fedex/, but I am not sure if this is the way of doing so.
Is there any GET call to get the estimated_delivery_date?
Thanks!

4

Hi,

Depending on which carriers you have, you can request rates using the url structure like you’ve shown. And yes, just as you’ve mentioned the API uses POST to return rates. There is no GET method for this route.

Here is the link to that specific section of the documentation for future reference: https://devapiverson.docs.apiary.io/#reference/rate.

Sophie

5

Hey, Sophie.

Thanks for replying.
Will any data be changed if I execute a POST like this?
apiverson.ordoro.com/order/](http://apiverson.ordoro.com/order/ORDER_NUMBER/rate/fedex/

Thanks!

6

Your order will remain intact and unchanged.

7

Thanks, Sophie.

  1. Should I consider the last ETA as the current one? (2018-10-26T20:00`:00+00:00) – please see the resulting json at the bottom of the message,
  2. what is the timezone?
  3. Why for the same orde Fedex site (https://www.fedex.com/apps/fedextrack/?action=track&action=track&language=english&last_action=alttrack&ascend_header=1&cntry_code=us&initial=x&mps=y&tracknumbers=783393391644) shows a different ETA: 10/25/2018 by 4:30 pm

Thanks,

[
    {
        "carrier": "fedex",
        "rate": 115.05,
        "estimated_delivery_date": "2018-10-24T08:00:00+00:00",
        "service_type": "FIRST_OVERNIGHT",
        "box_type": "FEDEX_PAK"
    },
    {
        "carrier": "fedex",
        "rate": 77.05,
        "estimated_delivery_date": "2018-10-24T10:30:00+00:00",
        "service_type": "PRIORITY_OVERNIGHT",
        "box_type": "FEDEX_PAK"
    },
    {
        "carrier": "fedex",
        "rate": 57.65,
        "estimated_delivery_date": "2018-10-24T20:00:00+00:00",
        "service_type": "STANDARD_OVERNIGHT",
        "box_type": "FEDEX_PAK"
    },
    {
        "carrier": "fedex",
        "rate": 36.95,
        "estimated_delivery_date": "2018-10-25T10:30:00+00:00",
        "service_type": "FEDEX_2_DAY_AM",
        "box_type": "FEDEX_PAK"
    },
    {
        "carrier": "fedex",
        "rate": 23.6,
        "estimated_delivery_date": "2018-10-25T20:00:00+00:00",
        "service_type": "FEDEX_2_DAY",
        "box_type": "FEDEX_PAK"
    },
    {
        "carrier": "fedex",
        "rate": 10.5,
        "estimated_delivery_date": "2018-10-26T20:00`:00+00:00",
        "service_type": "FEDEX_EXPRESS_SAVER",
        "box_type": "FEDEX_PAK"
    }
]
8
  1. Each Service Type will have its own Estimated Delivery Date, so the current one is whatever is in each rate in the response.
  2. The offset is +00:00 which is UTC.
  3. I’m not sure what the parameters given for that shipment are or what time zone conversion is taking place. These are the times returned by the carrier (FedEx) for an estimated delivery date based on the time that the rates were requested. If a label has already been created, I would expect its estimation could be different.
9

Thanks! I’ve found all the missing parts.