Skip to main content
Vindicia Knowledge Center

API Date Time Examples

API Date Time Returns

Today on our current Subscribe and Retain stack the system runs in PST and all API returns come back with a PST time and Offset.  Once the system moves into AWS these will change to UTC and the API will return back UTC time and offset.  

Example Soap Call 

Migration

Envelope

Before

{

   "object": "Account",

   "id": "Greg_Olive_REST",

   "vid": "5b498ea666a9b785ce53f5f149d5a20984770058",

   "created": "2020-12-01T14:26:47-08:00",

   "email_type": "html",

   "name": "Greg_Olive_REST"

}

After

{

   "object": "Account",

   "id": "Greg_Olive_REST",

   "vid": "5b498ea666a9b785ce53f5f149d5a20984770058",

   "created": "2020-12-01T22:26:47-00:00",

   "email_type": "html",

   "name": "Greg_Olive_REST"

}

Example Push Notification

Migration

Envelope

Before

"content":{"transactionItems":[{"taxClassification":"DV017194","taxType":"Exclusive Sales","servicePeriodStartDate":"2020-12-01T14:26:47-08:00","sku":"MONTHLY_1_DAY","name":"!!!! testing plan, daily billing, etc 

After

"content":{"transactionItems":[{"taxClassification":"DV017194","taxType":"Exclusive Sales","servicePeriodStartDate":"2020-12-01T22:26:47-00:00","sku":"MONTHLY_1_DAY","name":"!!!! testing plan, daily billing, etc 

How Subscribe / Retain define a day for future activity processing.

In Subscribe and Retain, a day is always from 00:00:01 to 23:59:59 as defined by the stack’s system time.  Prior to the AWS migration, production and prodtest stacks run in local Pacific Time.  Post the migration, our stacks will run on UTC Time.  The first second of the day (00:00:01), all activities for that day, regardless of their individual timestamps, become available for processing.  The system will process any activity that is available, as soon as the date matches and ignores the timestamp.  Post the migration, most activities will continue to occur on the same day, in UTC.  The example below illustrates the impact to the timing of the activities as part of the migration. For Activity #2 for example,  where the time zone translation results in the future activity now occurring on Wednesday (UTC time), processing will take place at 00:00:01 UTC on Wednesday.  

Timezone UTC Shift - Primary (3).png


 

Activity

Timestamp Before (PST)

Timestamp After (UTC)

After Migration when will activity be processed?

#1

Tue - 08:00:00 

Tue - 16:00:00

Tue 00:00:01 UTC - Same Day, 8 hours earlier

#2

Tue - 20:00:00

Wed - 04:00:00

Wed 00:00:01 UTC - Changes to next day, 16 hours later 

#3

Wed - 08:00:00

Wed - 16:00:00

Wed 00:00:01 UTC - Same Day, 8 hours earlier