Managing app & API service accounts costs | The place for Zendesk users to come together and share
Skip to main content
Solved

Managing app & API service accounts costs

  • May 19, 2026
  • 1 reply
  • 84 views

Matthew14

Our organization requires platform-to-platform-specific service user accounts  (eg Salesforce:Zendesk and Jira:Zendesk should be different accounts) for integrations in our security policies.

Based on guidance we received during initial implementation, it sounds like you need to allocate an agent seat for each integration. For instance, if you want to have individual service users that interface distinctly between Jira and Salesforce using their respective apps, or to operate within a middleware (necessary for storing credentials in non-app API workflows, since you can’t secure them in business rules), you need to pay for an agent seat for each.

Is that correct or can this be managed differently to better comply with enterprise data/platform security policies without paying for a dozen seat for “agents” that don’t exist?

Best answer by Ahmed Zaid

Hi ​@Matthew14 ,

Unfortunately, yes. The concept of service accounts does not exist in Zendesk currently and you will have to use a paid seat. You can save cost by using a dedicated admin account for all services like admin@yourcompany.com. Not best practice, but hasn’t presented an issue for me so far. I would only use it for administrative work though not working on tickets.

1 reply

Ahmed Zaid
  • User Group Leader
  • Answer
  • May 23, 2026

Hi ​@Matthew14 ,

Unfortunately, yes. The concept of service accounts does not exist in Zendesk currently and you will have to use a paid seat. You can save cost by using a dedicated admin account for all services like admin@yourcompany.com. Not best practice, but hasn’t presented an issue for me so far. I would only use it for administrative work though not working on tickets.