Service Account

A service account is a non-human identity used by an application, script, or server to authenticate to an API — as opposed to a personal user account tied to an individual. When your backend needs to call a third-party service on its own, unattended, it does so as a service account with its own credentials (usually a key pair or client secret) and its own set of permissions. The distinction matters for real operational reasons. A service account doesn't leave the company when an employee does, so your nightly sync won't break because someone offboarded. It can be scoped tightly to exactly the resources the integration needs, its keys can be rotated on a schedule without disrupting people, and its activity shows up separately in audit logs, making machine actions easy to distinguish from human ones. For SaaS builders wiring up server-to-server integrations — data pipelines, scheduled jobs, webhooks that call back — using a dedicated service account instead of a founder's personal token is the difference between a fragile hack and production-grade infrastructure.