Install Jentic One Beta

Connect the Planday.Platform.Api to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Planday.Platform.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%2Fplandayplatformapi%2Fplandayplatformapi" | sh

Step 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%2Fplandayplatformapi%2Fplandayplatformapi" | 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 Planday.Platform.Api.

Creates new booking for shift

Returns a Booking for a given bookingId

Departments_CreateDepartmentBydepartment

Departments_GetDepartmentsByquery.filter.search_queryquery.filter.include_delete

Departments_GetByid

GET STARTED

Start building with Planday.Platform.Api

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Planday.Platform.Api for, with concrete tasks.

★ Developer Tools Operations

Use the Planday.Platform.Api to perform developer tools operations programmatically. The API provides 46 endpoints covering core functionality including creates new booking for shift, returns a booking for a given bookingid, departments_createdepartmentbydepartment.

Call POST /Schedule/{departmentId}/shifts/{shiftId}/bookings to creates new booking for shift

Automated Booking Management

Automate booking operations by combining multiple Planday.Platform.Api endpoints. Agents can returns a booking for a given bookingid and then departments_createdepartmentbydepartment in a single workflow.

Call GET /Schedule/{departmentId}/bookings/{bookingInterestDescriptionId} to returns a booking for a given bookingid, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Planday.Platform.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 none tokens manually.

Search Jentic for 'creates new booking for shift', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

46 endpoints — planday.

METHOD

PATH

DESCRIPTION

POST

/Schedule/{departmentId}/shifts/{shiftId}/bookings

Creates new booking for shift

GET

/Schedule/{departmentId}/bookings/{bookingInterestDescriptionId}

Returns a Booking for a given bookingId

POST

/departments

Departments_CreateDepartmentBydepartment

GET

/departments

Departments_GetDepartmentsByquery.filter.search_queryquery.filter.include_delete

GET

/departments/{id}

Departments_GetByid

PUT

/departments/{id}

Departments_UpdateDepartmentByiddepartment

DELETE

/departments/{id}

Departments_DeleteByidremoveEmployees

GET

/departments/employees/{id}/departments

Departments_GetDepartmentsForEmployeeByid

POST

/Schedule/{departmentId}/shifts/{shiftId}/bookings

Creates new booking for shift

GET

/Schedule/{departmentId}/bookings/{bookingInterestDescriptionId}

Returns a Booking for a given bookingId

POST

/departments

Departments_CreateDepartmentBydepartment

GET

/departments

Departments_GetDepartmentsByquery.filter.search_queryquery.filter.include_delete

GET

/departments/{id}

Departments_GetByid

PUT

/departments/{id}

Departments_UpdateDepartmentByiddepartment

DELETE

/departments/{id}

Departments_DeleteByidremoveEmployees

GET

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Planday Platform API by hand means hand-building requests across its schedule, booking and department endpoints and threading whatever access header each call needs yourself. Through Jentic you install once, import the Planday Platform API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

The Planday Platform API puts the resource id in the URL path (/departments/{id}, /Schedule/{departmentId}/shifts/{shiftId}/bookings), so a rule can pin your agent to one department: it reads and books shifts for that department and nothing else. You choose the operations it may call, so destructive ones like deleting a department are not included unless you add them.

Credential isolation

Your Planday Platform credential 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 'create a booking for a shift' or 'list departments', and Jentic returns the matching Planday Platform operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Planday.Platform.Api through Jentic.

What authentication does the Planday.Platform.Api use?

The Planday.Platform.Api uses no authentication. 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 creates new booking for shift with the Planday.Platform.Api?

Yes. Use the POST /Schedule/{departmentId}/shifts/{shiftId}/bookings endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Planday.Platform.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 creates new booking for shift through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'creates new booking for shift'. Jentic returns the matching Planday.Platform.Api operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Planday.Platform.Api have?

The Planday.Platform.Api exposes 46 endpoints covering booking, departments, employees operations.

Can I limit what my agent is allowed to do with the Planday Platform API?

Yes. Because you run Jentic One yourself, your own rules decide which Planday Platform operations and credentials the agent may use. Since Planday puts the resource id in the URL path, such as /departments/{id} and /Schedule/{departmentId}/shifts/{shiftId}/bookings, you can pin the agent to a single department so it only reads and books shifts there. You also choose the exact operations it may call, so destructive ones like deleting a department stay out of reach unless you explicitly grant them.

Planday.Platform.Api

Name: Planday.Platform.Api
Brand: Planday.Platform.Api
Availability: InStock

Community OpenAPI document · agent-readyDeveloper ToolsSource Controlnone46 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically creates new booking for shift, returns a booking for a given bookingid. Covers 46 operations.

Use for: I need to creates new booking for shift, I want to returns a booking for a given bookingid, Search for departments_createdepartmentbydepartment, Find all departments_getdepartmentsbyquery.filter.search_queryquery.filter.include_delete

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

Planday.Platform.Api - OpenAPI Specification. The API exposes 46 endpoints.

Jentic One on Github View OpenAPI Document