Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Arbeidsforhold i oppdrag 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%2Farbeidsforhold-i-oppdrag-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%2Farbeidsforhold-i-oppdrag-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 Arbeidsforhold i oppdrag API.
Hent arbeidsforhold i oppdrag for person
Manage developer tools data programmatically
Integrate Arbeidsforhold i oppdrag API into automated workflows
Query and filter Arbeidsforhold i oppdrag API records by parameters
Monitor Arbeidsforhold i oppdrag API operational status and events
GET STARTED
Patterns agents use Arbeidsforhold i oppdrag API for, with concrete tasks.
★ Developer Tools Operations
Use the Arbeidsforhold i oppdrag API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including hent arbeidsforhold i oppdrag for person.
Call GET /{rettighetspakke}/arbeidsgiver/{organisasjonsnummer}/arbeidstaker/{foedselsnummer}/aktiv to hent arbeidsforhold i oppdrag for person
Data Retrieval and Monitoring
Query Arbeidsforhold i oppdrag 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 Arbeidsforhold i oppdrag API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Arbeidsforhold i oppdrag 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.
Search Jentic for 'hent arbeidsforhold i oppdrag for person', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — tjenesten leverer informasjon om hvorvidt det foreligger, og ev.
METHOD
PATH
DESCRIPTION
/{rettighetspakke}/arbeidsgiver/{organisasjonsnummer}/arbeidstaker/{foedselsnummer}/aktiv
Hent arbeidsforhold i oppdrag for person
/{rettighetspakke}/arbeidsgiver/{organisasjonsnummer}/arbeidstaker/{foedselsnummer}/aktiv
Hent arbeidsforhold i oppdrag for person
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Arbeidsforhold i oppdrag 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 i oppdrag API from the API Directory, store the token once, and your agent calls it.
Permission scoping
This API puts the employer organisation number and worker identifier in the URL path (/{rettighetspakke}/arbeidsgiver/{organisasjonsnummer}/arbeidstaker/{foedselsnummer}/aktiv), so a rule can pin your agent to one employer-worker pairing: it can read the active engagement for that pairing and nothing else. You choose the operations it may call, so a lookup for a different pairing is not included unless you add it.
Credential isolation
Your Arbeidsforhold i oppdrag 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.
Intent-based discovery
Agents search Jentic by intent such as 'hent arbeidsforhold i oppdrag for person' or 'read an active engagement for an employer and worker', and Jentic returns the matching Arbeidsforhold i oppdrag 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 Arbeidsforhold i oppdrag API through Jentic.
What authentication does the Arbeidsforhold i oppdrag API use?
The Arbeidsforhold i oppdrag 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 arbeidsforhold i oppdrag for person with the Arbeidsforhold i oppdrag API?
Yes. Use the GET /{rettighetspakke}/arbeidsgiver/{organisasjonsnummer}/arbeidstaker/{foedselsnummer}/aktiv endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Arbeidsforhold i oppdrag 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 arbeidsforhold i oppdrag for person through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'hent arbeidsforhold i oppdrag for person'. Jentic returns the matching Arbeidsforhold i oppdrag API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Arbeidsforhold i oppdrag API have?
The Arbeidsforhold i oppdrag API exposes 1 endpoints covering arbeidsgiver operations.
Can I limit what my agent is allowed to do with the Arbeidsforhold i oppdrag API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials your agent may use, and this API exposes only one operation: GET /{rettighetspakke}/arbeidsgiver/{organisasjonsnummer}/arbeidstaker/{foedselsnummer}/aktiv, which reads the active engagement for one employer-worker pairing. Since the employer organisation number and worker identifier sit in the URL path, you can pin your agent to a single pairing so it reads only that active engagement and nothing else. A lookup for a different pairing, or any other call, is not allowed unless you add it.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically hent arbeidsforhold i oppdrag for person. Covers 1 operations with bearer authentication.
Use for: I need to hent arbeidsforhold i oppdrag for person, Find available developer tools operations, Get the current status of Arbeidsforhold i oppdrag API resources, List all records from Arbeidsforhold i oppdrag API
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Tjenesten leverer informasjon om hvorvidt det foreligger, og ev. perioden for, et arbeidsforhold og mellom angitt oppdragsgiver og en angitt arbeidstaker. The API exposes 1 endpoints secured with bearer authentication.