Current User in Zendesk API Ticket Comments
Who is considered the current user when adding ticket comments via Zendesk APIs?
The current user is the one authenticating the API call. When you add ticket comments using Zendesk APIs, the current user is determined by who is authenticating the API call. This means that the user making the API call might not necessarily be the author of the comment.
If you're using the Tickets API with admin or agent credentials, the admin or agent is considered the current user for the ticket update. On the other hand, if you're using the Requests API with an end-user's identity and token, the end user is the current user for the ticket update. For more details, you can check out theoriginal article.
More related questions
Why aren't my business rules firing when using Zendesk API?
Business rules may not fire due to the current user condition. If your business rules are set to trigger based on the current user condition, they might not activate when tickets are created or updated using the API. This is because the current…
How does the current user affect ticket updates in Zendesk APIs?
The current user impacts who is recognized during ticket updates. In Zendesk APIs, the current user is the one authenticating the API call, which affects how ticket updates are processed. This user might not be the same as the comment author, which…
What is the difference between Tickets API and Requests API in Zendesk?
The difference lies in who is considered the current user. In Zendesk, the Tickets API and Requests API serve different purposes based on the user authenticating the call. The Tickets API is typically used with admin or agent credentials, making…
Interested indeflectingover 70% of your Zendesk support tickets?
Zendesk Support Tickets
Zendesk Messaging (live chat)
Join1,000+ companies reducing their support costs and freeing up support agents for more important work
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
Reduce support costs.Spend more time on customer success.
