Maqqie App Maqqie Platform Public API

Name: Maqqie Platform Public API
Brand: Maqqie Public API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingPayrolloauth213 EndpointsREST

For Agents

Onboard temporary workers, register their shift hours, and manage payroll placement definitions on the Maqqie platform via 13 endpoints. Authentication is OAuth 2.0 client credentials.

Install Jentic One Beta

Connect the Maqqie Platform Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Maqqie Platform Public 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 Maqqie Platform Public API.

Onboard a new temporary worker through /public/onboarding/v1/create-worker including their framework agreement

Update an existing worker's onboarding profile via /public/onboarding/v1/update-worker

Retrieve a worker's onboarding state with /public/onboarding/v1/get-worker-details before registering hours

GET STARTED

Start building with Maqqie Platform Public API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Maqqie Platform Public API, keeping it validated and agent-ready. The Maqqie Platform Public API lets third-party systems integrate with the Maqqie temporary-work payroll platform used in the Netherlands. It exposes endpoints for onboarding workers, registering hours and expenses for shifts and payroll placements, creating temporary-work payroll placement definitions, and managing hirer-side worker labels. The 13 endpoints are organised by sub-domain (onboarding, hours-and-expenses, temporary-work-payroll-placements, worker-profiles) and each endpoint is scoped to a specific role such as hirer.

Use Cases

Patterns agents use Maqqie Platform Public API for, with concrete tasks.

★ Temporary Worker Onboarding

Staffing agencies and hirers integrating with Maqqie call /public/onboarding/v1/create-worker and /public/onboarding/v1/create-framework-agreement to onboard temporary workers without manual data entry into the Maqqie back office. The endpoints accept the worker's identity and contract details and return the IDs needed for later hours registration. Initial integration takes 2-3 days including auth and error handling.

Call /public/onboarding/v1/create-worker with the worker's name, BSN, IBAN, and contract dates, then call /public/onboarding/v1/create-framework-agreement to attach the framework agreement and return the new worker ID.

Shift Hours Registration

Hirer scheduling tools call /public/hours-and-expenses/hirer/register-hours-for-shift-and-worker-simple-v1 at the end of each shift to push the hours actually worked into Maqqie's payroll engine. This replaces a manual paper sign-off with an automated submission and ensures workers are paid accurately on the standard payroll cycle. Integration is around a day for a single hirer.

Call /public/hours-and-expenses/hirer/register-hours-for-shift-and-worker-simple-v1 with shift ID 5587, worker ID 1024, and 7.5 hours worked, then return the registration confirmation ID.

Payroll Placement Setup

Hirer onboarding flows call /public/temporary-work-payroll-placements/hirer/create-temporary-work-payroll-placement-definition-for-user-minimal-v1 to set up the payroll placement that governs how a worker's hours convert into wages, taxes, and deductions. The minimal-v1 variant accepts the smallest required field set so a placement can be created without a full HR system feed.

Call /public/temporary-work-payroll-placements/hirer/create-temporary-work-payroll-placement-definition-for-user-minimal-v1 with user ID 1024, hourly rate 18.50 EUR, and a 12-week placement window.

Worker Tagging and Compliance

Hirer compliance teams use /public/worker-profiles/hirer/add-hirer-labels-to-worker-v1 to mark workers with certifications, depot assignments, or restrictions, and the matching remove endpoint when a label expires. These labels later drive shift eligibility checks in the hirer's scheduling tool.

Call /public/worker-profiles/hirer/add-hirer-labels-to-worker-v1 to add the 'forklift-certified' label to worker ID 1024 and confirm the label appears on a follow-up profile read.

AI Agent for Staffing Operations

An AI agent embedded in a hirer's scheduling or HR system calls Maqqie through Jentic to onboard workers, register hours, and manage labels without bespoke client code. Jentic exposes each Maqqie operation as a typed tool with a discoverable input schema so the agent invokes the right onboarding or hours endpoint without browsing api.maqqie.app docs.

Search Jentic for 'register shift hours on Maqqie', load the schema for /public/hours-and-expenses/hirer/register-hours-for-shift-and-worker-simple-v1, and execute the call for the latest completed shift.

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for maqqie platform public api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/public/onboarding/v1/create-worker

Onboard a new temporary worker

POST

/public/onboarding/v1/update-worker

Update an existing worker

GET

/public/onboarding/v1/get-worker-details

Read a worker's onboarding state

POST

/public/onboarding/v1/create-framework-agreement

Create a framework agreement

POST

/public/hours-and-expenses/hirer/register-hours-for-shift-and-worker-simple-v1

POST

/public/hours-and-expenses/hirer/register-hours-for-temporary-work-payroll-placement-simple-v1

POST

/public/temporary-work-payroll-placements/hirer/create-temporary-work-payroll-placement-definition-for-user-minimal-v1

Create a payroll placement for a user

POST

/public/worker-profiles/hirer/add-hirer-labels-to-worker-v1

Tag a worker with a hirer label

POST

/public/onboarding/v1/create-worker

Onboard a new temporary worker

POST

/public/onboarding/v1/update-worker

Update an existing worker

GET

/public/onboarding/v1/get-worker-details

Read a worker's onboarding state

POST

/public/onboarding/v1/create-framework-agreement

Create a framework agreement

POST

/public/hours-and-expenses/hirer/register-hours-for-shift-and-worker-simple-v1

Why Jentic?

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

Credential isolation

Maqqie OAuth 2.0 client credentials are stored encrypted in the Jentic vault (MAXsystem). Jentic exchanges them for a short-lived bearer token, attaches it to outgoing requests, and refreshes the token before expiry so the agent never handles the raw client secret.

Intent-based discovery

Agents search Jentic by intent (e.g. 'register shift hours' or 'onboard a temporary worker') and Jentic returns the matching Maqqie operations with their input schemas, so the agent picks the right onboarding or hours endpoint without browsing api.maqqie.app docs.

Time to first call

Direct Maqqie integration: 2-3 days to wire up OAuth, onboarding, hours registration, and error handling. Through Jentic: under an hour from search to first successful call.

FAQs

Specific to using Maqqie Platform Public API through Jentic.

Why is there no official OpenAPI spec for Maqqie Platform Public API?

Maqqie does not publish a hosted OpenAPI specification on its public website. Jentic generates and maintains this spec so that AI agents and developers can call Maqqie Platform Public API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Maqqie Public API use?

Maqqie uses OAuth 2.0 client credentials. The hirer or partner application requests an access token using its client ID and secret and supplies the bearer token on each call. Jentic stores the credentials in the MAXsystem vault and refreshes the token automatically.

Can I register hours for a temporary worker through the API?

Yes. POST to /public/hours-and-expenses/hirer/register-hours-for-shift-and-worker-simple-v1 for shift-based hours or /public/hours-and-expenses/hirer/register-hours-for-temporary-work-payroll-placement-simple-v1 for placement-based hours. The endpoints accept the worker, shift or placement ID, and hours worked.

What are the rate limits for the Maqqie Public API?

Maqqie does not publish a per-second rate limit in the spec. Quotas are negotiated per partner and enforced at the OAuth client level; refer to the Maqqie partner agreement for the limits assigned to your client ID.

How do I onboard a new worker through Jentic?

Run `pip install jentic`, search for 'onboard a worker on Maqqie', load the schema for POST /public/onboarding/v1/create-worker, and execute it with the worker's identity fields. Then call /public/onboarding/v1/create-framework-agreement to attach the framework agreement.

Does the API support tagging workers with hirer-specific labels?

Yes. The /public/worker-profiles/hirer/add-hirer-labels-to-user-v1 and /public/worker-profiles/hirer/add-hirer-labels-to-worker-v1 endpoints add labels and the matching remove endpoints take them off, which is typically used to mark certifications or depot assignments.

Maqqie App Maqqie Platform Public API

Connect the Maqqie Platform Public API to your agent

Capabilities

Start building with Maqqie Platform Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs