Auth API

Name: Auth API API
Brand: Auth API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthenticationbasic2 EndpointsREST

For Agents

Programmatically generate an access token, get the current version of the auth api. Covers 2 operations with basic authentication.

Use for: I need to generate an access token, I want to the current version of the auth api, Get the current status of Auth API resources, List all records from Auth API

Connect the Auth API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Auth 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 Auth API API.

Generate an access token

Get the current version of the Auth API

Integrate Auth API into automated workflows

Query and filter Auth API records by parameters

GET STARTED

Start building with Auth API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Auth API, keeping it validated and agent-ready.

This is Enables Authentication API which generates access tokens with credentials from Enables Identity and Acceess Management platform. These tokens then provide access to Enable other API offerings. </br></br>To read a walkthrough of how to use the API, <a href='https://api-developer.enable.net.nz/hc/en-nz/articles/32166117952409-How-to-use-the-API'>click here.</a>. The API exposes 2 endpoints secured with basic authentication.

Use Cases

Patterns agents use Auth API API for, with concrete tasks.

★ Identity and Authentication Operations

Use the Auth API to perform identity auth operations programmatically. The API provides 2 endpoints covering core functionality including generate an access token, get the current version of the auth api.

Call POST /token to generate an access token

Data Retrieval and Monitoring

Query Auth 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.

Poll the primary Auth API endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call Auth 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 basic tokens manually.

Search Jentic for 'generate an access token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

2 endpoints — this is enables authentication api which generates access tokens with credentials from enables identity and acceess management platform.

METHOD

PATH

DESCRIPTION

POST

/token

Generate an access token

GET

/version

Get the current version of the Auth API

POST

/token

Generate an access token

GET

/version

Get the current version of the Auth API

Why though Jentic?

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

Credential isolation

Auth API basic 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., 'generate an access token') and Jentic returns the matching Auth API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Auth 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

Auth0

Alternative identity auth API

Choose Auth0 when you need a different approach to identity auth operations

Alternative

Okta

Alternative identity auth API

Choose Okta when you need a different approach to identity auth operations

FAQs

Specific to using Auth API API through Jentic.

What authentication does the Auth API use?

The Auth API uses HTTP Basic authentication with username and password. 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 generate an access token with the Auth API?

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

What are the rate limits for the Auth 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 generate an access token through Jentic?

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

How many endpoints does the Auth API have?

The Auth API exposes 2 endpoints covering token, version operations.