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

# Skatteetaten Arbeidsforhold hendelser API

Tjeneste for uthenting av hendelser for Arbeidsforhold fra A-ordningen API. The API exposes 2 endpoints secured with bearer authentication.

## For AI agents

Programmatically hent hendelser for arbeidsforhold, hent startpunkt for hendelseslisten. Covers 2 operations with bearer authentication.

## Scope

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

## Capabilities

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

## Use cases

### Developer Tools Operations

Use the Arbeidsforhold hendelser API to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including hent hendelser for arbeidsforhold, hent startpunkt for hendelseslisten.

Example prompt: Call GET /hendelser to hent hendelser for arbeidsforhold

### Data Retrieval and Monitoring

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

### AI Agent Integration via Jentic

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/hendelser` | Hent hendelser for Arbeidsforhold |
| GET | `/hendelser/start` | Hent startpunkt for hendelseslisten |

## Key resources

- **Hendelser** — Operations for hendelser

## Why Jentic

- **Setup:** Wiring the Arbeidsforhold hendelser 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 hendelser API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** This API reads an event stream through query-driven operations rather than a resource id in the path, so you limit the agent to the operations it needs, such as reading employment-relationship events. You choose the operations it may call, so the start-of-stream operation is not included unless you add it.
- **Credential handling:** Your Arbeidsforhold hendelser 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 hendelser for arbeidsforhold' or 'read employment-relationship events', and Jentic returns the matching Arbeidsforhold hendelser 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 hendelser API use?

The Arbeidsforhold hendelser 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 hendelser for arbeidsforhold with the Arbeidsforhold hendelser API?

Yes. Use the GET /hendelser endpoint. The API returns structured JSON responses that agents can parse and act on directly.

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

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

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

The Arbeidsforhold hendelser API exposes 2 endpoints covering hendelser operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations and which stored credential the agent may use. This API reads an event stream through query-driven operations, so you can allow only reading employment-relationship events via GET /hendelser and leave out the start-of-stream operation, GET `/hendelser/start`, unless you add it. The agent can call only the operations you have permitted, and the bearer token is injected at execution time rather than exposed to the agent.
