canonical: https://jentic.com/apis/swaggerhub.jensmostaert3/api-of-the-adshot-uaa-service

# Jensmostaert3 API of the Adshot UAA service

This is the API definition for the Adshot UAA service. The API exposes 10 endpoints.

## For AI agents

Programmatically create a new user., list / search all users.. Covers 10 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Create a new user.
- List / search all Users.
- Retrieve details of a specific User.
- Update User account.
- Confirm the e-mail adress of a User.
- Request a token to reset a users password.
- Reset a users password.

## Use cases

### Developer Tools Operations

Use the API of the Adshot UAA service
 to perform developer tools operations programmatically. The API provides 10 endpoints covering core functionality including create a new user., list / search all users., retrieve details of a specific user..

Example prompt: Call POST `/v1/users` to create a new user.

### Automated Operations on Users Management

Automate operations on users operations by combining multiple API of the Adshot UAA service
 endpoints. Agents can list / search all users. and then retrieve details of a specific user. in a single workflow.

Example prompt: Call GET `/v1/users` to list / search all users., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API of the Adshot UAA service
 endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'create a new user.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/users` | Create a new user. |
| GET | `/v1/users` | List / search all Users. |
| GET | `/v1/users/{id}` | Retrieve details of a specific User. |
| PATCH | `/v1/users/{id}` | Update User account. |
| POST | `/v1/users/confirm_email` | Confirm the e-mail adress of a User. |
| POST | `/v1/users/password/reset_request` | Request a token to reset a users password. |
| POST | `/v1/users/password/reset` | Reset a users password. |
| GET | `/v1/user` | Retrieve the User resource owned by the authenticated user. |

## Key resources

- **Operations on Users** — User Controller
- **Authentication operations** — Authentication Controller

## Why Jentic

- **Setup:** Wiring the Adshot UAA service by hand means reading its spec, building calls across its user, email-confirmation, and password-reset endpoints, and handling request formatting and retries yourself. Through Jentic you install once, import the Adshot UAA service from the API Directory, store any required connection detail once, and your agent calls it.
- **Permission scoping:** Adshot UAA puts the user id in the URL path (`/v1/users/{id}`), so a rule can pin your agent to reading one user. You choose the operations it may call, so write operations like user creation, the PATCH update, or password reset are not included unless you add them.
- **Credential handling:** Any connection detail the Adshot UAA service needs is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a new user', and Jentic returns the matching Adshot UAA operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the API of the Adshot UAA service
 use?

The API of the Adshot UAA service
 uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create a new user. with the API of the Adshot UAA service
?

Yes. Use the POST `/v1/users` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the API of the Adshot UAA service
?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create a new user. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new user.'. Jentic returns the matching API of the Adshot UAA service
 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the API of the Adshot UAA service
 have?

The API of the Adshot UAA service
 exposes 10 endpoints covering operations on users, authentication operations operations.

### Can I limit what my agent is allowed to do with the Adshot UAA API?

Yes. Because you run Jentic One yourself, your own rules decide which Adshot UAA operations and credentials the agent may use, and it can only call the ones you grant. Since the user id sits in the URL path at GET `/v1/users/{id}`, you can pin the agent to reading a single user while leaving write operations like POST `/v1/users`, the PATCH update, and the password reset endpoints out of scope. You add those operations only if and when you choose to.