canonical: https://jentic.com/apis/swaggerhub.alayacare/authorizations-external-api # Alayacare Authorizations External API The external API for the authorizations feature in api.scheduler. The API exposes 7 endpoints. ## For AI agents Programmatically creates a new authorization, fetches a list of authorizations. Covers 7 operations. ## Scope Does not handle payments, communications, or crm - use for productivity only. ## Capabilities - Creates a new authorization - Fetches a list of authorizations - Updates an existing authorization - Deactivates an Authorization - Retrieves medicaid IDs for specific client - It returns the utilization status of an item. ## Use cases ### Productivity Operations Use the Authorizations External API to perform productivity operations programmatically. The API provides 7 endpoints covering core functionality including creates a new authorization, fetches a list of authorizations, updates an existing authorization. Example prompt: Call POST /authorizations to creates a new authorization ### Automated Authorizations Management Automate authorizations operations by combining multiple Authorizations External API endpoints. Agents can fetches a list of authorizations and then updates an existing authorization in a single workflow. Example prompt: Call GET /authorizations to fetches a list of authorizations, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Authorizations External 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 none tokens manually. Example prompt: Search Jentic for 'creates a new authorization', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /authorizations | Creates a new authorization | | GET | /authorizations | Fetches a list of authorizations | | PUT | /authorizations/{authorization_id} | Updates an existing authorization | | DELETE | /authorizations/{authorization_id} | Deactivates an Authorization | | POST | /authorizations/medicaid_ids | Retrieves medicaid IDs for specific client | | GET | /authorizations/{authorization_id}/usages | Fetches a list of authorizations Usage | | POST | /authorizations/items/utilization_status | It returns the utilization status of an item. | ## Key resources - **Authorizations** — Operations related to Authorizations - **Authorizations Usages** — Operations related to Authorizations Usages - **Item Utilization Status** — Operations related to Item Utilization Status ## Why Jentic - **Setup:** Wiring the Authorizations External API by hand means mapping its authorization operations onto the hosted scheduler host and calling each create, update, delete, and usage lookup yourself. Through Jentic you install once, import the Authorizations External API from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** The Authorizations External API puts the authorization id in the URL path (/authorizations/{authorization_id}), so a rule can pin your agent to one authorization: it can read its usages and nothing else. You choose the operations it may call, so ones that change or remove data like update or delete are not included unless you add them. - **Credential handling:** Your Authorizations External API 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 'create a new authorization' or 'get an authorization's usages', and Jentic returns the matching Authorizations External API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Asana** — Alternative productivity API - **Monday** — Alternative productivity API - **Clickup** — Complementary productivity API ## FAQ ### What authentication does the Authorizations External API use? The Authorizations External API 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 creates a new authorization with the Authorizations External API? Yes. Use the POST /authorizations endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Authorizations External 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 creates a new authorization through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'creates a new authorization'. Jentic returns the matching Authorizations External API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Authorizations External API have? The Authorizations External API exposes 7 endpoints covering authorizations, authorizations usages, item utilization status operations. ### Can I limit what my agent is allowed to do with the Authorizations External API? Yes. Because you run Jentic One yourself, your own rules decide which Authorizations External API operations and credentials the agent may use. Since the authorization ID sits in the URL path (/authorizations/{authorization_id}), you can pin an agent to a single authorization and let it only read that authorization's usages. Operations that change or remove data, such as updating (PUT) or deactivating (DELETE) an authorization, are excluded unless you explicitly grant them.