Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Jason Blood
Beigetreten 23. Nov. 2022
·
Letzte Aktivität 09. Jan. 2025
Folge ich
0
Follower
0
Gesamtaktivitäten
5
Stimmen
0
Abonnements
2
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Jason Blood
Jason Blood hat einen Post erstellt
We are trying to send a webhook event in which a webhook is triggered when a ticket moves to closed or resolved status. In the webhook event data we would like to include the tickets last comment from an agent (or even include an additional field that indicates what type of user the last comment was sent from. E.g. support agent, or the requester for example. Is this possible.
My attempt to do this is doing the following in the body of the webhook
```
{
"ticket_id":"{{ticket.id}}",
"ticket_subject":"{{ticket.title}}",
"ticket_status":"{{ticket.status}}",
"last_agent_response":"{{ticket.latest_public_comment}}",
"closed_at":"{{ticket.updated_at}}"
}
```
Esentially I want to store in by backend service when a zendesk ticket is closed or resolved, what was the last comment left by a zendesk admin or agent that was visible to the end user / requester
Gepostet 09. Jan. 2025 · Jason Blood
1
Follower
0
Stimmen
0
Kommentare
Jason Blood hat einen Post erstellt
Howdy we are using the api
api/v2/requests
to create tickets in our backend in zendesk. The volume is generally pretty low that we are sending to this endpoint as far as we can see on our end. But we are still seeing cases during certain parts of the day where we get a spike of failed requests due to a 429 status code . I have been reading through the documentation but couldn't find any specific rate limits mentioned being applied to this endpoint specifically. Is there any.
I have attached a screenshot of our api activity graph and we are no where close to our requests per minute. So surprised we are getting rate limited.
Gepostet 14. Dez. 2022 · Jason Blood
0
Follower
4
Stimmen
1
Kommentar
Jason Blood hat einen Post erstellt
Hi I am using the following endpoint
/api/v2/requests
to create zendesk tickets on our account. We have the tickets creating correctly and correctly populating a number of custom fields. But one of our fields does not seem to populate. The field in question is a drop down field with multiple possible values.
I am following the docs here around custom fields.
and like I said other custom fields are working correctly.
I have attached the below json of the custom field that we are sending.
```
{
"custom_fields": [
{
"id": 10767612515085, "value":"orders__live_recording_request__order_fulfillment_"
}
]
}
```
I have redacted the other custom fields from that json that are working. But for some reason when the ticket is submitted the field is never populated in the side bar of the form. I have double checked the id field is correct. E.g the form field id. And the value is the tag of the selected value. So at a lose for what I am doing wrong :(
Gepostet 23. Nov. 2022 · Jason Blood
0
Follower
4
Stimmen
3
Kommentare