Loket.nl API

Name: Loket.nl API
Brand: Loket.nl API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingPayrolloauth2641 EndpointsREST

For Agents

Read and update Dutch employer payroll, employee, leave, and absence records on Loket.nl across 641 endpoints scoped to employments, payroll runs, leave policies, and chamber-of-commerce lookups.

Install Jentic One Beta

Connect the Loket.nl API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Loket.nl 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Loket.nl API.

Acquire employer and employee directory data including chamber-of-commerce company information and address lookups by postal code

Manage employments, contracts, and wage components per employee with versioned payroll periods

Administer leave policies, leave requests, leave balances, and collective leave events for an employer

GET STARTED

Start building with Loket.nl API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Loket.nl API for, with concrete tasks.

★ Dutch payroll provider onboarding

Partner software that runs payroll for Dutch SMEs uses the Loket.nl API to enrol new employers, sync the employee directory, and post wage components to the correct payroll periods. The API exposes 641 endpoints covering employments, contracts, and statutory reporting, so a partner can replace manual data entry between their HR product and Loket. Most integrations stand up the read flow first, then add write operations once acceptance-environment validation passes.

List employments for employer X, then post a new wage component for employee 12345 in the current payroll period and confirm the entry appears under that employment.

Leave and absence self-service

HR portals built on top of Loket use the leave and absence endpoints to let employees submit leave requests, see their accrued balance, and track open absences. The API distinguishes leave policies, leave balances, leave requests, and collective leave so a portal can render the right view per employer policy. Integration is typically a few days because the leave domain is well-tagged and uses consistent identifiers.

Get the leave balance for employee 12345 as of today, submit a leave request for 3 days next month, and confirm the request status changes to pending.

HR data warehouse extract

Analytics teams use the directory, employment, and payroll endpoints to extract a daily snapshot of headcount, contract types, and payroll movements into a warehouse. Because Loket exposes provider authorisation and application sets, the extract job can run with a scoped partner identity rather than a user session. The volume of endpoints (641) means agents typically iterate by tag rather than path-by-path.

Pull the list of providers and application sets for an employer, then iterate through employees and pull each active employment record into a flat structure.

Agent-driven leave assistant via Jentic

An AI assistant in a workplace chat answers questions like 'how much leave do I have left?' and 'submit a sick day for me' by calling Loket through Jentic. Jentic loads the employee, leave-balance, and leave-request endpoints into the agent's tool list and isolates the OAuth tokens, so the assistant never sees raw credentials. Going from prompt to working assistant takes under an hour with Jentic versus several days handling Loket's OAuth flow directly.

Use Jentic to search 'submit a leave request', load the Loket leave-request operation, and execute it with employee, start date, end date, and leave-type values from the conversation.

Key Endpoints

641 endpoints — loket.

METHOD

PATH

DESCRIPTION

GET

/providers

List partner providers configured for an employer

PUT

/providers/applicationsets/{applicationSetId}

Edit an application set's details

GET

/applications/{applicationId}/authorizations

List authorisations for a partner application

GET

/aowDate

Acquire the Dutch state pension (AOW) date for a person

GET

/chamberofcommerce/{chamberOfCommerceNumber}/companyinformation

Look up company information by KvK number

GET

/locationservices/address

Resolve a postal code and house number to a Dutch address

GET

/achmeainsurancecontracts

List Achmea insurance contracts for an employer

GET

/providers

List partner providers configured for an employer

PUT

/providers/applicationsets/{applicationSetId}

Edit an application set's details

GET

/applications/{applicationId}/authorizations

List authorisations for a partner application

GET

/aowDate

Acquire the Dutch state pension (AOW) date for a person

GET

/chamberofcommerce/{chamberOfCommerceNumber}/companyinformation

Look up company information by KvK number

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Loket OAuth client and user credentials are stored encrypted in the Jentic vault. Agents call operations using a scoped access token issued by Jentic — partner client secrets and refresh tokens never enter the agent's context.

Intent-based discovery

Agents search by intent (for example 'submit a leave request' or 'list employments') and Jentic returns the matching Loket operation with its input schema, so the agent does not need to navigate 641 endpoints by hand.

Time to first call

Direct Loket integration: 1-2 weeks for OAuth flow, acceptance-environment validation, and tag-by-tag endpoint discovery. Through Jentic: under 1 hour — search by intent, load schema, execute against acceptance or production.

FAQs

Specific to using Loket.nl API through Jentic.

What authentication does the Loket.nl API use?

The Loket.nl API uses OAuth 2.0 — partners receive client credentials and individual users complete a user-credential flow against the Loket OAuth server. Through Jentic, refresh tokens stay in the credential vault and the agent only ever receives a short-lived scoped access token, so raw client secrets never enter agent context.

Can I submit a leave request through the Loket.nl API?

Yes. The leave domain exposes leave-request operations under endpoints tagged Leave, Leave request, and Leave balance, so you can create a request, query its status, and pull the resulting balance change. Use Jentic search 'submit a leave request' to load the operation directly.

What are the rate limits for the Loket.nl API?

Loket does not publish a public rate limit number; partners are expected to validate against the acceptance environment (api.loket-acc.nl) before pointing production traffic at api.loket.nl. If a request is throttled, Loket returns standard HTTP 429 — Jentic's executor surfaces that response unchanged so the agent can back off.

How do I look up Dutch company information through Loket via Jentic?

Loket exposes a chamber-of-commerce lookup at /chamberofcommerce/{chamberOfCommerceNumber}/companyinformation. Search Jentic for 'chamber of commerce company information', load the operation, and execute it with the KvK number to receive the registered company record.

Does the Loket.nl API cover Dutch state pension (AOW) calculations?

It exposes the AOW date for a given person via /aowDate but does not run the wider state pension calculation itself — combine it with the employment and wage endpoints if you need to derive expected retirement-related payroll changes.

How many endpoints does the Loket.nl API have?

641 unique path-and-method combinations across employments, leave, absence, providers, payroll, and reference data. Tag-based discovery is the fastest path: ask Jentic for the area you need (for example 'leave balance') rather than browsing the full path list.