Enterprise Admin Service API

Name: Enterprise Admin Service API API
Brand: Enterprise Admin Service API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controloauth25 EndpointsREST

For Agents

Programmatically run, run1. Covers 5 operations with oauth2 authentication.

Connect the Enterprise Admin Service API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Enterprise Admin Service API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Enterprise Admin Service API API.

Run

Manage developer tools data programmatically

Integrate Enterprise Admin Service API into automated workflows

Query and filter Enterprise Admin Service API records by parameters

GET STARTED

Start building with Enterprise Admin Service API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Enterprise Admin Service API API for, with concrete tasks.

★ Developer Tools Operations

Use the Enterprise Admin Service API to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including run, run1, run2.

Call POST /CreateUser to run

Automated Create User Management

Automate create user operations by combining multiple Enterprise Admin Service API endpoints. Agents can run1 and then run2 in a single workflow.

Call GET /GetCompanyById to run1, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Enterprise 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.

Search Jentic for 'run', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — enterprise admin service api.

METHOD

PATH

DESCRIPTION

POST

/CreateUser

Run

GET

/GetCompanyById

Run1

POST

/GetUserAuthorizations

Run2

GET

/GetUserByObjectId

Run4

GET

/GetUsersByCompanyId

Run3

POST

/CreateUser

Run

GET

/GetCompanyById

Run1

POST

/GetUserAuthorizations

Run2

GET

/GetUserByObjectId

Run4

GET

/GetUsersByCompanyId

Run3

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Enterprise Admin Service API oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'run') and Jentic returns the matching Enterprise Admin Service API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Enterprise Admin Service API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Enterprise Admin Service API API through Jentic.

What authentication does the Enterprise Admin Service API use?

The Enterprise Admin Service API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I run with the Enterprise 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 Enterprise 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 run through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'run'. Jentic returns the matching Enterprise Admin Service API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Enterprise Admin Service API have?

The Enterprise Admin Service API exposes 5 endpoints covering create user, get user authorizations details, get user details operations.