Skatteetaten betjeningskartet-ikutlegg-sit-synt
Browse all Swaggerhub Skatteetaten APIsCommunity OpenAPI document · agent-readyDeveloper ToolsSource Controlbearer4 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically registrerer påbegynt saksbehandling, endre parter i sak som er låst til et gitt regelverk. Covers 4 operations with bearer authentication.
Use for: I need to registrerer påbegynt saksbehandling, I want to endre parter i sak som er låst til et gitt regelverk, Search for registrerer saksbehandling avsluttet, Find all sjekker om en skyldner skal behandles etter tidligere eller nytt regelverk
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
betjeningskartet-ikutlegg-sit-synt. The API exposes 4 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the betjeningskartet-ikutlegg-sit-synt to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the betjeningskartet-ikutlegg-sit-synt, 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.
1
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%2Fbetjeningskartet-ikutlegg-sit-synt" | sh2
Step 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%2Fbetjeningskartet-ikutlegg-sit-synt" | 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.
Capabilities
What an agent can do with betjeningskartet-ikutlegg-sit-synt API.
Registrerer påbegynt saksbehandling
Endre parter i sak som er låst til et gitt regelverk
Sjekker om en skyldner skal behandles etter tidligere eller nytt regelverk
Query and filter betjeningskartet-ikutlegg-sit-synt records by parameters
Monitor betjeningskartet-ikutlegg-sit-synt operational status and events
Use Cases
Patterns agents use betjeningskartet-ikutlegg-sit-synt API for, with concrete tasks.
★ Developer Tools Operations
Use the betjeningskartet-ikutlegg-sit-synt to perform developer tools operations programmatically. The API provides 4 endpoints covering core functionality including registrerer påbegynt saksbehandling, endre parter i sak som er låst til et gitt regelverk, registrerer saksbehandling avsluttet.
Call POST /api/v1/betjeningskartet/saksbehandling/startsak to registrerer påbegynt saksbehandling
Automated betjeningskartet-controller Management
Automate betjeningskartet-controller operations by combining multiple betjeningskartet-ikutlegg-sit-synt endpoints. Agents can endre parter i sak som er låst til et gitt regelverk and then registrerer saksbehandling avsluttet in a single workflow.
Call POST /api/v1/betjeningskartet/saksbehandling/endrepart to endre parter i sak som er låst til et gitt regelverk, then verify the result
AI Agent Integration via Jentic
AI agents discover and call betjeningskartet-ikutlegg-sit-synt 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.
Search Jentic for 'registrerer påbegynt saksbehandling', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
4 endpoints — betjeningskartet-ikutlegg-sit-synt.
METHOD
PATH
DESCRIPTION
POST
/api/v1/betjeningskartet/saksbehandling/startsak
Registrerer påbegynt saksbehandling
POST
/api/v1/betjeningskartet/saksbehandling/endrepart
Endre parter i sak som er låst til et gitt regelverk
POST
/api/v1/betjeningskartet/saksbehandling/avsluttsak
Registrerer saksbehandling avsluttet
POST
/api/v1/betjeningskartet
Sjekker om en skyldner skal behandles etter tidligere eller nytt regelverk
POST
/api/v1/betjeningskartet/saksbehandling/startsak
Registrerer påbegynt saksbehandling
POST
/api/v1/betjeningskartet/saksbehandling/endrepart
Endre parter i sak som er låst til et gitt regelverk
POST
/api/v1/betjeningskartet/saksbehandling/avsluttsak
Registrerer saksbehandling avsluttet
POST
/api/v1/betjeningskartet
Sjekker om en skyldner skal behandles etter tidligere eller nytt regelverk
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring betjeningskartet-ikutlegg-sit-synt by hand means implementing STS JWT bearer auth, targeting its skead.no service host, and writing your own request and retry handling. Through Jentic you install once, import betjeningskartet-ikutlegg-sit-synt from the API Directory, store the token once, and your agent calls it.
Permission scoping
This API drives case handling through operations that carry their details in the request body rather than a resource id in the path, so you limit the agent to the operations it needs, such as starting a case or changing a party. You choose the operations it may call, so closing a case is not included unless you add that operation.
Credential isolation
Your betjeningskartet-ikutlegg-sit-synt 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.
Intent-based discovery
Agents search Jentic by intent such as 'registrerer paabegynt saksbehandling' or 'change a party on a case', and Jentic returns the matching betjeningskartet-ikutlegg-sit-synt operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using betjeningskartet-ikutlegg-sit-synt API through Jentic.
What authentication does the betjeningskartet-ikutlegg-sit-synt use?
The betjeningskartet-ikutlegg-sit-synt 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 registrerer påbegynt saksbehandling with the betjeningskartet-ikutlegg-sit-synt?
Yes. Use the POST /api/v1/betjeningskartet/saksbehandling/startsak endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the betjeningskartet-ikutlegg-sit-synt?
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 registrerer påbegynt saksbehandling through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'registrerer påbegynt saksbehandling'. Jentic returns the matching betjeningskartet-ikutlegg-sit-synt operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the betjeningskartet-ikutlegg-sit-synt have?
The betjeningskartet-ikutlegg-sit-synt exposes 4 endpoints covering betjeningskartet-controller operations.
Can I limit what my agent is allowed to do with the Betjeningskartet API?
Yes. Because you run Jentic One yourself, your own rules decide which of the Betjeningskartet operations the agent may call and which credentials it may use. You can allow only the operations the agent needs, such as starting a case with POST /api/v1/betjeningskartet/saksbehandling/startsak or changing a party with POST /api/v1/betjeningskartet/saksbehandling/endrepart, and withhold others like closing a case with POST /api/v1/betjeningskartet/saksbehandling/avsluttsak. The bearer token stays under your control and is injected only for the operations you have permitted.
GET STARTED