canonical: https://jentic.com/apis/tieto.com/tieto

# Tieto Lifecare Welfare API Services / Elderly care

tieto.com/main version V1. The API exposes 129 endpoints.

## For AI agents

Programmatically gets a actualization by the unique identifier., gets a list of actualizations.. Covers 129 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Gets a actualization by the unique identifier.
- Creates a new client file.
- Integrate Lifecare Welfare API Services / Elderly care into automated workflows
- Query and filter Lifecare Welfare API Services / Elderly care records by parameters
- Monitor Lifecare Welfare API Services / Elderly care operational status and events

## Use cases

### Developer Tools Operations

Use the Lifecare Welfare API Services / Elderly care to perform developer tools operations programmatically. The API provides 129 endpoints covering core functionality including gets a actualization by the unique identifier., gets a list of actualizations., gets a list of elderly care business logs..

Example prompt: Call GET `/api/v1/actualizations/{id}` to gets a actualization by the unique identifier.

### Automated Actualizations Management

Automate actualizations operations by combining multiple Lifecare Welfare API Services / Elderly care endpoints. Agents can gets a list of actualizations. and then gets a list of elderly care business logs. in a single workflow.

Example prompt: Call GET `/api/v1/actualizations` to gets a list of actualizations., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Lifecare Welfare API Services / Elderly care 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 'gets a actualization by the unique identifier.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v1/actualizations/{id}` | Gets a actualization by the unique identifier. |
| GET | `/api/v1/actualizations` | Gets a list of actualizations. |
| GET | `/api/v1/business-logs/elderly-care` | Gets a list of elderly care business logs. |
| GET | `/api/v1/client_absences/{id}` | Gets a client absence by its ID. |
| GET | `/api/v1/client_absences` | Gets a list of client absences. |
| GET | `/api/v1/client_critical_informations` | Gets a list of client critical informations. |
| POST | `/api/v1/client_files` | Creates a new client file. |
| GET | `/api/v1/clients/{id}` | Gets a client by the social security number. |

## Key resources

- **Actualizations** — Operations for actualizations
- **Business Logs** — Operations for business logs
- **Client_Absences** — Operations for client_absences
- **Client_Critical_Informations** — Operations for client_critical_informations
- **Client_Files** — Operations for client_files

## Why Jentic

- **Setup:** Wiring the Lifecare Welfare API Services / Elderly care API by hand means targeting its tieto.com integration host and building the actualization, client, and business-log calls yourself, even though these endpoints define no API credential. Through Jentic you install once, import the Lifecare Welfare API Services / Elderly care API from the API Directory, and your agent calls it.
- **Permission scoping:** Lifecare puts the resource id in the URL path (`/api/v1/clients/{id}`, `/api/v1/actualizations/{id}`), so a rule can pin your agent to one record: it can read that client or actualization and nothing else. You choose the operations it may call, so a write like posting a client file is not included unless you add it.
- **Credential handling:** These operations define no API credential, so there is nothing to store. Your own Jentic One instance still applies any required request handling at execution time, and nothing sensitive enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get an actualization by id' or 'look up a client', and Jentic returns the matching Lifecare Welfare API Services / Elderly care operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Lifecare Welfare API Services / Elderly care use?

The Lifecare Welfare API Services / Elderly care 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 gets a actualization by the unique identifier. with the Lifecare Welfare API Services / Elderly care?

Yes. Use the GET `/api/v1/actualizations/{id}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Lifecare Welfare API Services / Elderly care?

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 gets a actualization by the unique identifier. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'gets a actualization by the unique identifier.'. Jentic returns the matching Lifecare Welfare API Services / Elderly care operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Lifecare Welfare API Services / Elderly care have?

The Lifecare Welfare API Services / Elderly care exposes 129 endpoints covering actualizations, business logs, client_absences operations.

### Can I limit what my agent is allowed to do with the Lifecare Welfare API Services / Elderly care?

Yes. Jentic One is self-hosted, so your own rules decide which Lifecare operations and records the agent may touch. Because the API puts the resource id in the URL path, such as GET `/api/v1/clients/{id}` and GET `/api/v1/actualizations/{id}`, you can pin the agent to a single client or actualization and let it read that record and nothing else. You also choose the operations it may call, so a write like POST `/api/v1/client_files` is not available to the agent unless you add it.