canonical: https://jentic.com/apis/swaggerhub.skatteetaten/boligsparing-for-ungdom-api

# Skatteetaten Boligsparing for ungdom API

Tjenesten leverer informasjon om BSU renteinntekter pr kalenderår for en person. The API exposes 1 endpoints secured with bearer authentication.

## For AI agents

Programmatically hent boligsparing for ungdom for person. Covers 1 operations with bearer authentication.

## Scope

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

## Capabilities

- Hent boligsparing for ungdom for person
- Manage developer tools data programmatically
- Integrate Boligsparing for ungdom API into automated workflows
- Query and filter Boligsparing for ungdom API records by parameters
- Monitor Boligsparing for ungdom API operational status and events

## Use cases

### Developer Tools Operations

Use the Boligsparing for ungdom API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including hent boligsparing for ungdom for person.

Example prompt: Call GET /{rettighetspakke}/{inntektsaar}/{foedselsnummer} to hent boligsparing for ungdom for person

### Data Retrieval and Monitoring

Query Boligsparing for ungdom 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 Boligsparing for ungdom API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Boligsparing for ungdom 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 bearer tokens manually.

Example prompt: Search Jentic for 'hent boligsparing for ungdom for person', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/{rettighetspakke}/{inntektsaar}/{foedselsnummer}` | Hent boligsparing for ungdom for person |

## Why Jentic

- **Setup:** Wiring the Boligsparing for ungdom API by hand means implementing Maskinporten JWT bearer auth, choosing between the skatteetaten-test.no and production skatteetaten.no hosts, and writing your own retry handling. Through Jentic you install once, import Boligsparing for ungdom API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** This API puts the person's national identity number in the URL path (/{rettighetspakke}/{inntektsaar}/{foedselsnummer}), so a rule can pin your agent to one person: it can read the youth housing savings for that person and year and nothing else. You choose the operations it may call, so a lookup for a different person is not included unless you add it.
- **Credential handling:** Your Boligsparing for ungdom API token 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 'hent boligsparing for ungdom for person' or 'read youth housing savings for a person and year', and Jentic returns the matching Boligsparing for ungdom API 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 Boligsparing for ungdom API use?

The Boligsparing for ungdom API uses a Bearer token in the Authorization header. 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 hent boligsparing for ungdom for person with the Boligsparing for ungdom API?

Yes. Use the GET /{rettighetspakke}/{inntektsaar}/{foedselsnummer} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Boligsparing for ungdom 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 hent boligsparing for ungdom for person through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'hent boligsparing for ungdom for person'. Jentic returns the matching Boligsparing for ungdom API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Boligsparing for ungdom API have?

The Boligsparing for ungdom API exposes 1 endpoints for developer tools operations.

### Can I limit what my agent is allowed to do with the Boligsparing for ungdom API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials your agent may use, and this API has just one operation: GET /{rettighetspakke}/{inntektsaar}/{foedselsnummer}, which reads a person's youth housing savings for a given income year. Since the national identity number sits in the URL path, your rule can pin the agent to a single person and year so it reads only that record and nothing else. A lookup for a different person or year is not available to the agent unless you add it.