Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Innrapportering boligselskap API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.skatteetaten%2Finnrapportering-boligselskap-api" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.skatteetaten%2Finnrapportering-boligselskap-api" | 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.
What an agent can do with Innrapportering boligselskap API.
Lever tredjepartsopplysninger for et boligselskap
Hent ut dokument (attachment i dialogporten)
Integrate Innrapportering boligselskap API into automated workflows
Query and filter Innrapportering boligselskap API records by parameters
Monitor Innrapportering boligselskap API operational status and events
GET STARTED
Patterns agents use Innrapportering boligselskap API for, with concrete tasks.
★ Developer Tools Operations
Use the Innrapportering boligselskap API to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including lever tredjepartsopplysninger for et boligselskap, hent ut dokument (attachment i dialogporten).
Call POST /{inntektsaar} to lever tredjepartsopplysninger for et boligselskap
Data Retrieval and Monitoring
Query Innrapportering boligselskap 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.
Poll the primary Innrapportering boligselskap API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Innrapportering boligselskap 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.
Search Jentic for 'lever tredjepartsopplysninger for et boligselskap', load the operation schema, and execute with Jentic-managed credentials
2 endpoints — tjeneste for innrapportering av tredjepartsopplysninger for et boligselskap fra sluttbrukersystemer.
METHOD
PATH
DESCRIPTION
/{inntektsaar}
Lever tredjepartsopplysninger for et boligselskap
/{inntektsaar}/forsendelser/{forsendelseId}/dokumenter/{dokumentId}
Hent ut dokument (attachment i dialogporten)
/{inntektsaar}
Lever tredjepartsopplysninger for et boligselskap
/{inntektsaar}/forsendelser/{forsendelseId}/dokumenter/{dokumentId}
Hent ut dokument (attachment i dialogporten)
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Innrapportering boligselskap 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 boligselskap 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 isolation
Any Innrapportering boligselskap 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.
Intent-based discovery
Agents search Jentic by intent such as 'lever tredjepartsopplysninger for et boligselskap' or 'read a submitted report document', and Jentic returns the matching Innrapportering boligselskap API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using Innrapportering boligselskap API through Jentic.
What authentication does the Innrapportering boligselskap API use?
The Innrapportering boligselskap 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 boligselskap with the Innrapportering boligselskap 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 boligselskap 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 boligselskap 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 boligselskap'. Jentic returns the matching Innrapportering boligselskap API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Innrapportering boligselskap API have?
The Innrapportering boligselskap API exposes 2 endpoints covering boligselskap operations.
Can I limit what my agent is allowed to do with the Innrapportering boligselskap API?
Yes. Because Jentic One is self-hosted, your own rules decide which of this API's operations and credentials the agent may use. This API has two operations: submitting third-party reports for an income year with POST /{inntektsaar}, and reading a submitted document by its ids with GET /{inntektsaar}/forsendelser/{forsendelseId}/dokumenter/{dokumentId}. You choose which of these the agent can call, so you can allow only document reads and leave the submit operation out unless you explicitly add it.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically lever tredjepartsopplysninger for et boligselskap, hent ut dokument (attachment i dialogporten). Covers 2 operations.
Use for: I need to lever tredjepartsopplysninger for et boligselskap, I want to hent ut dokument (attachment i dialogporten), Get the current status of Innrapportering boligselskap API resources, List all records from Innrapportering boligselskap API
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Tjeneste for innrapportering av tredjepartsopplysninger for et boligselskap fra sluttbrukersystemer. The API exposes 2 endpoints.