API returning timestamps without timezone information

  • 1
  • Idea
  • Updated 3 years ago
  • Under Consideration
  • (Edited)
The Emma API is generating timestamps in Central time but without timezone offset info in the timestamp itself.

For example, I had a mailing go out yesterday at 6pm GMT+8, or 5am Central.

Using the mailings API this is the information I received for this mailing:

(
    [mailing_type] => m
    [send_started] => @D:2015-07-02T05:00:19
    [started_or_finished] => @D:2015-07-02T05:00:19
    [send_at] => @D:2015-07-02T05:00:00
)
I would expect the timestamp to be one of the following for less ambiguous parsing:
  1. Unix Timestamp
  2. Atomic timestamp (eg @D:2015-07-02T05:00:00-05:00)
I should note that this isn't a big issue as long it's well-documented that all timestamps returned are in Central time (and I presume this will be either CDT or CST depending on the time of year), but it would be preferable if the timezone offset was included in the timestamp, such that using strtotime() would immediately generate the correct Unix timestamp.

(As an aside, could I enquire as to why the "@D:" prefix is necessary?)
Photo of Joel Pan

Joel Pan

  • 29 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 1
Photo of Katie Lewis

Katie Lewis, Official Rep

  • 3414 Posts
  • 309 Reply Likes
Hi Joel! I'm looking into this for you and will let you know what I find out.
Photo of Katie Lewis

Katie Lewis, Official Rep

  • 3414 Posts
  • 309 Reply Likes
Hi Joel! We'd like to tackle this work soon, so we're looking at how the sub-teams (focused on certain places in the app) within our Product Team are arranged to figure out the best fit for this work and groom it.

I'll let you know when there's more news to share, and thank you for pointing this out!