Visit Freshworks.com Visit Freshworks

Topics started by adivs1625

2 Topics

A
Contributor
adivs1625Contributor
posted in Archives - Freshdesk

Freshdesk "ticket_activities" API discrepancy in export time

Hi Team,API for exporting ticket_activities responds with -1. "created_at": "27-10-2018",2. "url": xxxxxxxWhen we redirect to URL, it shows a metadata key-value as - "metadata": {        "start_at": "27-10-2018 18:30:00 +0000",        "end_at": "28-10-2018 18:29:59 +0000",        "activities_count": xx    }I wish to know that how -1. created_at is on 27-10 while the data captured is of 27-10 and 28-10 ?2. Is metadata->start_at timestamp is in UTC ?3. If (2) is true, then why the first response (created_at) timestamp is not in UTC ?

0
A
Contributor
5 years ago
A
Contributor
adivs1625Contributor
posted in Archives - Freshdesk

Freshdesk API for ticket_activities - Need clarity !!

Hi, for a custom report export, we have a and API endpoint "ticket_activities" which basically show us the change log of all tickets.I need to know the following:1. How many activities can be received as response ?2. Is it Paginated ?3. What are the possible fields which will be part of response, for consumption on client side ?

11
aravind.sundararajan
Skilled Expert
5 years ago

Badge winners

Show all badges
Terms of UseCookie settings