canonical: https://jentic.com/apis/swaggerhub.uday730/admin-service-api

# Uday730 Admin Service API

Admin Service API provides programmatic access to developer tools functionality. The API exposes 1 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically createuser. Covers 1 operations with oauth2 authentication.

## Scope

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

## Capabilities

- CreateUser
- Manage developer tools data programmatically
- Integrate Admin Service API into automated workflows
- Query and filter Admin Service API records by parameters
- Monitor Admin Service API operational status and events

## Use cases

### Developer Tools Operations

Use the Admin Service API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including createuser.

Example prompt: Call POST /CreateUser to createuser

### Data Retrieval and Monitoring

Query Admin Service API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Admin Service API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Admin Service API 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 oauth2 tokens manually.

Example prompt: Search Jentic for 'createuser', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/CreateUser` | CreateUser |

## Key resources

- **Create User** — Operations related to Create User

## Why Jentic

- **Setup:** Wiring the Admin Service API by hand means implementing its OAuth2 flow, managing token refresh against the Azure API Management host, and building your own retries around the create user call. Through Jentic you install once, import the Admin Service API from the API Directory, store the OAuth2 credentials once, and your agent calls it.
- **Permission scoping:** Limit the agent to the operations it needs, such as creating a user, rather than the whole surface. Because you pick the allowed operations, the agent only ever runs the calls you authorize.
- **Credential handling:** Your Admin Service OAuth2 credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter 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 Admin Service 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 Admin Service API use?

The Admin Service API uses OAuth 2.0 for authorization. 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 createuser with the Admin Service API?

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

### What are the rate limits for the Admin Service API?

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 createuser through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'createuser'. Jentic returns the matching Admin Service API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Admin Service API have?

The Admin Service API exposes 1 endpoints covering create user operations.

### Can I limit what my agent is allowed to do with the Admin Service API?

Yes. The Admin Service API is run through Jentic One, which you self-host, so your own rules decide which operations and credentials the agent may use. You can grant the agent only the calls it needs, such as POST /CreateUser to create a user, instead of the full API surface. The agent runs only the operations you authorize, and the OAuth 2.0 credentials are injected at execution time rather than exposed to the agent.