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

# Skatteetaten Arbeidsforhold API

Tjenesten leverer informasjon om arbeidsgivers (opplysningspliktiges) innrapporterte arbeidsforholdsopplysninger for en inntektsmottaker for en gitt periode. The API exposes 2 endpoints secured with bearer authentication.

## For AI agents

Programmatically hent arbeidsforholdsopplysninger for inntektsmottaker, hent arbeidsforholdsopplysninger for gitt id. Covers 2 operations with bearer authentication.

## Scope

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

## Capabilities

- Hent arbeidsforholdsopplysninger for inntektsmottaker
- Manage developer tools data programmatically
- Integrate Arbeidsforhold API into automated workflows
- Query and filter Arbeidsforhold API records by parameters
- Monitor Arbeidsforhold API operational status and events

## Use cases

### Developer Tools Operations

Use the Arbeidsforhold API to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including hent arbeidsforholdsopplysninger for inntektsmottaker, hent arbeidsforholdsopplysninger for gitt id.

Example prompt: Call GET /{rettighetspakke}/person/{personidentifikator} to hent arbeidsforholdsopplysninger for inntektsmottaker

### Data Retrieval and Monitoring

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

### AI Agent Integration via Jentic

AI agents discover and call Arbeidsforhold 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 arbeidsforholdsopplysninger for inntektsmottaker', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/{rettighetspakke}/person/{personidentifikator}` | Hent arbeidsforholdsopplysninger for inntektsmottaker |
| GET | `/{rettighetspakke}/{aggregatId}` | Hent arbeidsforholdsopplysninger for gitt ID |

## Key resources

- **Person** — Operations for person

## Why Jentic

- **Setup:** Wiring the Arbeidsforhold 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 Arbeidsforhold API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** This API puts the person identifier or aggregate id in the URL path (/{rettighetspakke}/person/{personidentifikator}, /{rettighetspakke}/{aggregatId}), so a rule can pin your agent to reads for one subject: it can fetch employment records for that person or aggregate and nothing else. You choose the operations it may call, so a lookup for a different subject is not included unless you add it.
- **Credential handling:** Your Arbeidsforhold 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 arbeidsforholdsopplysninger for inntektsmottaker' or 'read employment records for a person', and Jentic returns the matching Arbeidsforhold 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 Arbeidsforhold API use?

The Arbeidsforhold 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 arbeidsforholdsopplysninger for inntektsmottaker with the Arbeidsforhold API?

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

### What are the rate limits for the Arbeidsforhold 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 arbeidsforholdsopplysninger for inntektsmottaker through Jentic?

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

### How many endpoints does the Arbeidsforhold API have?

The Arbeidsforhold API exposes 2 endpoints covering person operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which operations and credentials your agent may use with the Arbeidsforhold API. Because this API carries the subject in the URL path, you can allow only the two read operations, GET /{rettighetspakke}/person/{personidentifikator} and GET /{rettighetspakke}/{aggregatId}, and pin the agent to fetching employment records for a single person or aggregate. A lookup for a different subject or any other call is not available to the agent unless you explicitly add it.