canonical: https://jentic.com/apis/swaggerhub.skatteetaten/betjeningskartet-ikutlegg-sit-synt

# Skatteetaten betjeningskartet-ikutlegg-sit-synt

betjeningskartet-ikutlegg-sit-synt. The API exposes 4 endpoints secured with bearer authentication.

## For AI agents

Programmatically registrerer påbegynt saksbehandling, endre parter i sak som er låst til et gitt regelverk. Covers 4 operations with bearer authentication.

## Scope

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

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'registrerer påbegynt saksbehandling', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **betjeningskartet-controller** — Operations related to betjeningskartet-controller

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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.