Skip to main content
Question

Anybody have issues with API calls and "Invitee_Start_Time_Pretty"?

  • August 19, 2025
  • 1 reply
  • 69 views
C

In referencing this API documentation:
https://calendly.stoplight.io/docs/api-docs-v1/c2NoOjE4NzA3MzM-webhook-payload

It says the following: “Human-readable moment when the event starts in invitee's timezone (e.g. "12:00pm - Wednesday, March 14, 2018")”

This should mean that the webhook payload data here contains the start time for the invitee, so if this was pulled out of a payload and sent in an email, it wouldn’t be confusing to the invitee regarding what time their meeting is at.

Ours, however, ALWAYS sends this in pacific time. We have tested internally with 3 different employees in different time zones and all three have ended up with the invitee start time showing pacific time. Our Calendly is set to mountain time, as well as our Zoho Flow (although this shouldn’t affect anything).

What is more interesting, is in the same exact payload, a field titled, “timezone” (the timezone of the invitee) comes across with the correct timezone.

Any ideas?

 

1 reply

T
Employee

Hi Chris!
 

My name is Taylor, and I'm a Developer Support Specialist with Calendly.

Thanks for calling this out and for testing it across multiple time zones.
 

Based on what you shared, this does not look like a case of Calendly sending the wrong invitee timezone value. In our webhook data, the canonical datetime fields are sent as structured timestamps, and the invitee timezone is provided separately as an IANA timezone value such as America/New_York.
 

What stands out here is that you’re seeing the issue in Zoho Flow, and we do have internal guidance that Zoho generates its own human-readable “pretty” time fields rather than passing those through directly from Calendly. Our internal support guidance for the Zoho Flow integration specifically notes reports of Zoho-generated “pretty” fields appearing in Pacific Time even when the separate timezone field is correct.
 

So in this scenario, the most likely issue is not that Calendly is translating the time incorrectly for Google or Outlook. It is more likely that Zoho Flow is reformatting the webhook data on its side, while the raw timestamp and timezone values from Calendly remain correct.
 

Moving forward, my recommendation would be to:

  • Treat the raw datetime field plus the timezone field as the source of truth.

  • Reach out to Zoho Support to review how Zoho Flow is generating the pretty/human-readable time fields.

  • You’re also welcome to email support@calendly.com with your examples so we can help spearhead the investigation alongside you and compare what Calendly is sending versus what Zoho is displaying.

 

Hope this helps point you in the right direction.

 

Enroll in Calendly’s Research Community” style= Need Help? Visit 'Get Help. Give Help.'
Terms & ConditionsAccessibility statement