> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/api-reference/add-a-user-for-infinity-api-access.md).
# Creating Eseye API users and credentials
Before you can call the Eseye Infinity APIs, they need a **service account**. A service account holds machine credentials, a Client ID and a Client Secret, that your application uses to authenticate against the API. It sits separately from the portal logins your team uses to sign in.
### Prerequisite
Your portal account must have permission to manage user accounts. If **User Accounts** does not appear under **Portfolio**, contact your administrator.
### Create the service account
1. Go to the [Infinity portal](https://infinity.anynetiot.com/mfe/infinity/dashboard).
2. Select **Portfolio** > **User accounts**.
3. Select **Actions** > **Service Accounts** > **Actions** > **Add new user**.
4. Enter the email address, first name and last name, then select the access roles the application needs.
5. Select **Save**.
### Copy the client credentials
After you save the account, Infinity displays your Client ID and Secret.
{% hint style="warning" %}
**Important:** Copy and securely store the Client ID and Secret before you close the page. You cannot recall them once the page is closed on Infinity.
{% endhint %}
You use these details to sign in to the Eseye SIM Validation Suite (Tabby).
### Replace a lost client secret
You cannot view or recover a client secret after closing the confirmation window. If you lose it:
1. Delete the existing service account.
2. Create a new service account.
3. Update the application with the new client ID and client secret.
Confirm that the credentials are no longer in use before deleting a service account.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.eseye.com/api-reference/add-a-user-for-infinity-api-access.md?ask=&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 `automate deployments from our CI pipeline` 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.
