Re: updatedAt and createdAt does not have timezone information

Anonymous
Not applicable

updatedAt and createdAt does not have timezone information

While getting lead information via any of the "GET" REST APIs, I see that both createdAt and updatedAt does not contain any timezone information as described in the API example.  For instance, "Get Lead By ID" says to return:
  1. {
  2. "requestId":"e42b#14272d07d78",
  3. "success":true,
  4. "result":[
  5. {
  6. "id":60,
  7. "email":"kjashaedd@klooblept.com",
  8. "firstName":"Kataldar",
  9. "updatedAt":"2013-11-21T11:47:30-08:00"
  10. }
  11. ]
  12. }
However, I get the following:

{
  "requestId": "3eae#14ce8b9cffd",
  "result": [
    {
      "id": 1,
      "updatedAt": "2015-04-09 21:20:15",
      "lastName": "xxxx",
      "email": "xxx.xxx@xxxxx.com",
      "createdAt": "2015-04-09 21:14:03",
      "firstName": "xxxx"
    }
  ],
  "success": true
}

As you can see my results have no timezone.  So, the problem for me is that when requesting "Lead Changes", the API needs the time with timezone when using the Paging Token API:
 
 ParametersRequired/OptionalDescription

sinceDatetime

Required

Supported datetime format:

2014-10-06T13:22:17-08:00

2014-10-06T13:22-07:00

2014-10-06


Is there anyway to get the timezone from a lead object?
Tags (1)
1 REPLY 1
Anonymous
Not applicable

Re: updatedAt and createdAt does not have timezone information

Hi Mario

I tried and I have seen timezone is lacked.
I think this is a API bug.
By the way SOAP API timezone is GMT-5:00 everytime. Regardless of US summer time.
I think this REST API's timezone is GMT-5:00 everytime too.