canonical: https://jentic.com/apis/swaggerhub.enable-networks/auth-api # Enable Networks Auth API 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.

To read a walkthrough of how to use the API, click here.. The API exposes 2 endpoints secured with basic authentication. ## For AI agents Programmatically generate an access token, get the current version of the auth API. Covers 2 operations with basic authentication. ## Scope Does not handle payments, communications, or crm - use for identity and authentication only. ## Capabilities - 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 - Monitor Auth API operational status and events ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'generate an access token', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /token | Generate an access token | | GET | /version | Get the current version of the Auth API | ## Key resources - **token** — Operations related to token - **version** — Operations related to version ## Why Jentic - **Setup:** Wiring the Auth API by hand means encoding its HTTP basic credentials, calling the token endpoint against the Enable Networks host, and handling the response yourself. Through Jentic you install once, import the Auth API from the API Directory, store the basic credential once, and your agent calls it. - **Permission scoping:** The Auth API exposes a token endpoint and a version endpoint that take their inputs in the request body, so scope your agent to the operations it needs, such as generating an access token: you choose the operations it may call, so nothing beyond them is available. - **Credential handling:** Your Auth API basic credential 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 'generate an access token', and Jentic returns the matching Auth API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Auth0** — Alternative identity auth API - **Okta** — Alternative identity auth API ## FAQ ### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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. ### Can I limit what my agent is allowed to do with the Auth API? Yes. Because you run Jentic One yourself, your own rules decide which Auth API operations and credentials the agent may use. The Auth API exposes only two operations, generating an access token via POST /token and reading the current version via GET /version, so you can grant your agent just token generation and withhold everything else. Your basic credential is stored encrypted by your own instance and injected only when a permitted operation runs.