> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/platform-administration/service-accounts.md).

# Service accounts

- [Service accounts](https://docs.snyk.io/platform-administration/service-accounts/service-accounts.md): Snyk service accounts for non-interactive API access, available on Enterprise plans
- [Choose a service account type to use with Snyk APIs](https://docs.snyk.io/platform-administration/service-accounts/choose-a-service-account-type-to-use-with-snyk-apis.md): How to choose a Snyk service account type and level, based on the permissions your API automation needs
- [Service accounts using OAuth 2.0](https://docs.snyk.io/platform-administration/service-accounts/service-accounts-using-oauth-2.0.md): How to create and use Snyk service accounts with OAuth 2.0, available on Enterprise plans through the Snyk API
- [Manage service accounts using the Snyk API](https://docs.snyk.io/platform-administration/service-accounts/manage-service-accounts-using-the-snyk-api.md): How to create and manage Snyk service accounts through the Snyk REST API, including the required permissions


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/platform-administration/service-accounts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.