canonical: https://jentic.com/apis/swaggerhub.skatteetaten/innrapportering-boligsameie-api

# Skatteetaten Innrapportering boligsameie API

Tjeneste for innrapportering av tredjepartsopplysninger for et boligsameie fra sluttbrukersystemer. The API exposes 2 endpoints.

## For AI agents

Programmatically lever tredjepartsopplysninger for et boligsameie, hent ut dokument (attachment i dialogporten). Covers 2 operations.

## Scope

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

## Capabilities

- Lever tredjepartsopplysninger for et boligsameie
- Hent ut dokument (attachment i dialogporten)
- Integrate Innrapportering boligsameie API into automated workflows
- Query and filter Innrapportering boligsameie API records by parameters
- Monitor Innrapportering boligsameie API operational status and events

## Use cases

### Developer Tools Operations

Use the Innrapportering boligsameie API to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including lever tredjepartsopplysninger for et boligsameie, hent ut dokument (attachment i dialogporten).

Example prompt: Call POST /{inntektsaar} to lever tredjepartsopplysninger for et boligsameie

### Data Retrieval and Monitoring

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

### AI Agent Integration via Jentic

AI agents discover and call Innrapportering boligsameie 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 none tokens manually.

Example prompt: Search Jentic for 'lever tredjepartsopplysninger for et boligsameie', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/{inntektsaar}` | Lever tredjepartsopplysninger for et boligsameie |
| GET | `/{inntektsaar}/forsendelser/{forsendelseId}/dokumenter/{dokumentId}` | Hent ut dokument (attachment i dialogporten) |

## Key resources

- **boligsameie** — Operations related to boligsameie

## Why Jentic

- **Setup:** Wiring the Innrapportering boligsameie API by hand means reading the Skatteetaten docs, choosing between the skatteetaten-test.no and production skatteetaten.no hosts, and writing your own request and retry handling even though the endpoints are open. Through Jentic you install once, import Innrapportering boligsameie API from the API Directory, store any needed access detail once, and your agent calls it.
- **Permission scoping:** This API submits reports for an income year from the request body and reads a document by ids in the URL path (/{inntektsaar}/forsendelser/{forsendelseId}/dokumenter/{dokumentId}), so you limit the agent to the operations it needs, such as reading a submitted document. You choose the operations it may call, so submitting a report is not included unless you add the POST operation.
- **Credential handling:** Any Innrapportering boligsameie API access detail 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 'lever tredjepartsopplysninger for et boligsameie' or 'read a submitted report document', and Jentic returns the matching Innrapportering boligsameie 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 Innrapportering boligsameie API use?

The Innrapportering boligsameie API 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 lever tredjepartsopplysninger for et boligsameie with the Innrapportering boligsameie API?

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

### What are the rate limits for the Innrapportering boligsameie 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 lever tredjepartsopplysninger for et boligsameie through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'lever tredjepartsopplysninger for et boligsameie'. Jentic returns the matching Innrapportering boligsameie API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Innrapportering boligsameie API have?

The Innrapportering boligsameie API exposes 2 endpoints covering boligsameie operations.

### Can I limit what my agent is allowed to do with the Innrapportering boligsameie API?

Yes. Jentic One is self-hosted by you, so your own rules decide which of the API's two operations the agent may call and which credentials it may use. This API submits third-party reports for an income year with POST /{inntektsaar} and reads a submitted document by its ids with GET /{inntektsaar}/forsendelser/{forsendelseId}/dokumenter/{dokumentId}, so you can grant the agent only the read operation while withholding the submit operation. The POST operation is included only if you explicitly add it.