Alayacare Care Plan 2.0
Browse all Swaggerhub Alayacare APIs★ Only Publicly Available OpenAPI DocumentHealthcareClinical Databasic38 EndpointsREST
For Agents
Programmatically create a care plan using the client alayacare id, get a list of care plan base information using the client alayacare id. Covers 38 operations with basic authentication.
Use for: I need to a care plan using the client alayacare id, I want to a list of care plan base information using the client alayacare id, Search for a care plan using the client external id, Find all a list of care plan base information using the client external id
Not supported: Does not handle payments, communications, or crm — use for healthcare only.
External Clinical API **Internal IDs** The following terms are used to reference IDs that identify resources in AlayaCare: - id - created_by - client_id - employee_id - plan_id - diagnosis_id - goal_id - intervention_id **External IDs** The following terms are used to reference IDs that identify resources systems external to AlayaCare: - external_employee_id - external_client_id - external_service. The API exposes 38 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the Care Plan 2.0 to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Care Plan 2.0, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: 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 | sh2
Step 2: 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 instanceJentic 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 Care Plan 2.0 API.
Create a care plan using the client Alayacare ID
Get a list of care plan base information using the client Alayacare ID
Integrate Care Plan 2.0 into automated workflows
Query and filter Care Plan 2.0 records by parameters
Monitor Care Plan 2.0 operational status and events
Use Cases
Patterns agents use Care Plan 2.0 API for, with concrete tasks.
★ Healthcare Operations
Use the Care Plan 2.0 to perform healthcare operations programmatically. The API provides 38 endpoints covering core functionality including create a care plan using the client alayacare id, get a list of care plan base information using the client alayacare id, create a care plan using the client external id.
Call POST /client/{client_id}/careplans to create a care plan using the client alayacare id
Automated Careplans Management
Automate careplans operations by combining multiple Care Plan 2.0 endpoints. Agents can get a list of care plan base information using the client alayacare id and then create a care plan using the client external id in a single workflow.
Call GET /client/{client_id}/careplans to get a list of care plan base information using the client alayacare id, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Care Plan 2.0 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 'create a care plan using the client alayacare id', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
38 endpoints — external clinical api **internal ids** the following terms are used to reference ids that identify resources in alayacare: - id - created_by - client_id - employee_id - plan_id - diagnosis_id - goal_id - intervention_id **external ids** the following terms are used to reference ids that identify resources systems external to alayacare: - external_employee_id - external_client_id - external_service.
METHOD
PATH
DESCRIPTION
POST
/client/{client_id}/careplans
Create a care plan using the client Alayacare ID
GET
/client/{client_id}/careplans
Get a list of care plan base information using the client Alayacare ID
POST
/client/by_id/{external_client_id}/careplans
Create a care plan using the client external ID
GET
/client/by_id/{external_client_id}/careplans
Get a list of care plan base information using the client external ID
GET
/client/{client_id}/careplans/active
Get the detailed information of the active care plan using Alayacare client ID
GET
/client/{client_id}/careplans/currently-active
Get the detailed information of the active care plan using Alayacare client ID
GET
/client/by_id/{external_client_id}/careplans/active
Get the detailed information of the active care plan using client external ID
GET
/client/by_id/{external_client_id}/careplans/currently-active
Get the detailed information of the active care plan using client external ID
POST
/client/{client_id}/careplans
Create a care plan using the client Alayacare ID
GET
/client/{client_id}/careplans
Get a list of care plan base information using the client Alayacare ID
POST
/client/by_id/{external_client_id}/careplans
Create a care plan using the client external ID
GET
/client/by_id/{external_client_id}/careplans
Get a list of care plan base information using the client external ID
GET
/client/{client_id}/careplans/active
Get the detailed information of the active care plan using Alayacare client ID
GET
/client/{client_id}/careplans/currently-active
Get the detailed information of the active care plan using Alayacare client ID
GET
/client/by_id/{external_client_id}/careplans/active
Get the detailed information of the active care plan using client external ID
GET
/client/by_id/{external_client_id}/careplans/currently-active
Get the detailed information of the active care plan using client external ID
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Care Plan 2.0 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., 'create a care plan using the client alayacare id') and Jentic returns the matching Care Plan 2.0 operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Care Plan 2.0 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.
FAQs
Specific to using Care Plan 2.0 API through Jentic.
What authentication does the Care Plan 2.0 use?
The Care Plan 2.0 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 create a care plan using the client alayacare id with the Care Plan 2.0?
Yes. Use the POST /client/{client_id}/careplans endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Care Plan 2.0?
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 create a care plan using the client alayacare id through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create a care plan using the client alayacare id'. Jentic returns the matching Care Plan 2.0 operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Care Plan 2.0 have?
The Care Plan 2.0 exposes 38 endpoints covering careplans, client, forms operations.
GET STARTED