**AlayaCare IDs:** The following terms are used to reference IDs that identify resources in AlayaCare: - id - visit_id - premium_id - visit_premium_id - employee_id - cost_centre_id - client_id **External IDs** The following terms are used to reference IDs that identify resources systems external to AlayaCare: - employee_external_id - client_external_id External IDs are required to be unique. No o. The API exposes 65 endpoints secured with basic authentication.
65 endpoints**Internal IDs:** The following terms are used to reference IDs that identify resources in AlayaCare: - account_id - client_user_id **External IDs:** External IDs are required to be unique. No other assumptions are made regarding their form; they are treated as strings. The following terms are used to reference IDs that identify resources in systems external to AlayaCare: - external_client_id - ex. The API exposes 5 endpoints secured with basic authentication.
5 endpointsThe external API for the authorizations feature in api.scheduler. The API exposes 7 endpoints.
7 endpointsThis end point can be used to create, edit and retrieve billable items before they can be processed in invoices. The API exposes 22 endpoints secured with basic authentication.
22 endpointsExternal 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.
38 endpointsCMS 485 integration api. The API exposes 8 endpoints.
8 endpointsswaggerhub.alayacare/api-medication-external version 1.2.0. The API exposes 9 endpoints secured with basic authentication.
9 endpointsStep 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 | shStep 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.