canonical: https://jentic.com/apis/swaggerhub.skatteetaten/aktiv-konto-api

# Skatteetaten Aktiv konto API

Tjenesten leverer informasjon om valgt konto for utbetalinger av beløp til gode fra Skatteetaten. The API exposes 1 endpoints secured with bearer authentication.

## For AI agents

Programmatically hent aktiv konto for person. Covers 1 operations with bearer authentication.

## Scope

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

## Capabilities

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

## Use cases

### Developer Tools Operations

Use the Aktiv konto API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including hent aktiv konto for person.

Example prompt: Call GET /{rettighetspakke}/{personidentifikator} to hent aktiv konto for person

### Data Retrieval and Monitoring

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

### AI Agent Integration via Jentic

AI agents discover and call Aktiv konto 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 aktiv konto for person', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/{rettighetspakke}/{personidentifikator}` | Hent aktiv konto for person |

## Why Jentic

- **Setup:** Wiring the Aktiv konto 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 Aktiv konto API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** This API puts the person identifier in the URL path (/{rettighetspakke}/{personidentifikator}), so a rule can pin your agent to one person: it can read the active account for that person 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 Aktiv konto 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 aktiv konto for person' or 'read the active account for a person', and Jentic returns the matching Aktiv konto 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 Aktiv konto API use?

The Aktiv konto 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 aktiv konto for person with the Aktiv konto API?

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

### What are the rate limits for the Aktiv konto 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 aktiv konto 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 aktiv konto for person'. Jentic returns the matching Aktiv konto API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Aktiv konto API have?

The Aktiv konto API exposes 1 endpoints for developer tools operations.

### Can I limit what my agent is allowed to do with the Aktiv konto API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this API exposes only GET /{rettighetspakke}/{personidentifikator} to read the active account for a person. Since the person identifier sits in the URL path, you can pin the agent to a single person so it reads only that account and nothing else. A lookup for a different person is not available to the agent unless you add that operation yourself.