Fares

Let me guess, this is not on the roadmap for 2025 either ?

Hi Samantha,

So you are saying if I want to get a single EST day I have to send two request for two UTC days and then work the code to extract from those two responses the portion that is my single EST day ?

I hope you can see how unwieldy and unusable this is for anyone not living in UTC.

Fares

Hey Samantha,

The documentation I received specifies the following : 

Additonnaly, when calling the endpoint with a different start and end time parameters, I get an explicit error :

  "message": {

    "startTime": [

      "The start time field must be a date equal to end time."

    ]

What am I missing in this case ?

Thank you,

Fares

Hello,

Thank you for giving me access to this API.

I've started experimeting with it and I want to understand exactly which 24 hours are included when I enter a Unix timestamp, with regards to timezones.

Let's take a practical example . 

The timestamp 1734488584 corresponds to early 18th December in GMT and late 17th December in EST (which is the timezone configured in my Zendesk settings).

If I send a request with that timestamp in both startTime and endTime parameters, will the result covers the whole 18th of december in GMT or the whole 17th December in EST ?

I could certainly figure the answer out by running tests but timezones give me headache and as we're still configuring WFM, I don't have users generating data to help those tests (and don't know of another way to generate time entries).

Thank you,

Fares

Hey Gabriel, thank you for the answer. I will keep an eye out.

Hello,

Is ti possible to create a trigger or automation that automatically deletes empty tickets created when users mention us in their instagram story? It's a pain to have tickets in the view that are not actual messages.