290d1b34-xxxx-xxxx-xxxx-294cc2eb049eĪpex Geoff also has a modern REST API V2.1 Connect configuration. Consequently, the XML returned for the legacy Connect listener shows Eastern Time. This is a setting DocuSign support must set. Years ago, a former admin on Apex Geoff’s account asked DocuSign to set the timezone for Connect webhook requests to Eastern time. To complicate the story of this envelope more, we will assume that Apex Geoff has a legacy Connect setup with a listener in New York. Since Greenbeard is the sender of the envelope, the COC is written in his time zone as defined in his preferences. Note that the time zone stamped on the COC is (UTC-10:00) Hawaii. It is the same for both Apex Geoff and Greenbeard or any other viewer.
This image below shows the Certificate of Completion (COC). In his user preferences he has chosen Hawaii as his time zone and a 24-hour time display format.
The next image shows Green Beard’s view of Envelope History for this same envelope. He has not set a time zone in his preferences, so the time zone comes from his computer. The image below shows Apex Geoff viewing the same envelope’s history. This is a snippet of the REST API GET Envelope response for this envelope once the envelope is completed: "emailSubject": "Please DocuSign: _Test.pdf", Likewise, the response will use UTC dates. These would be provided in UTC date format. He could get the envelope information using an envelopeId or by making an API call, providing from_date and to_date query parameters. Both are signers and both sign the envelope.Īpex Geoff might use the eSignature REST API to get envelope information. Greenbeard sends an envelope to Apex Geoff. The administrator has set the account Regional Settings to the following: The administrator for the account is Apex Geoff, who lives on the US West Coast. This article will explain the variations.įor my example, Green Beard is a user who lives in Hawaii. Developer Support has had several conversations with developers who were trying to understand the ways time is presented in DocuSign. Users who view envelopes in the eSignature web application, however, will have multiple variations on how timestamps show up for them. If you make a GET API call to retrieve an envelope’s details, the time included in the response is in UTC.
Next time change is highlighted.ĭata for the years before 1970 is not available for The Purchase, however, we have earlier time zone history for New York available.The DocuSign eSignature REST API always uses UTC time. Time Changes in The Purchase Over the Yearsĭaylight Saving Time (DST) changes do not necessarily occur on the same date every year. The graph above illustrates clock changes in The Purchase during 2023.
0 kommentar(er)
