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 them the current user for ticket updates.
On the other hand, the Requests API is used with an end-user's identity and token, making the end user the current user. Choosing the right API depends on your project's needs and who should be recognized as the current user during updates.
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…
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…
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…