Install Jentic One Beta

Connect the Parkalot API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Parkalot 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%2Fparkalot.io%2Fparkalot" | 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%2Fparkalot.io%2Fparkalot" | 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 Parkalot API.

Retrieve parking reservations in nested (grouped by day/item) or flat (one period per record) formats

Create or release parking spot reservations in batch operations with waitlist support

Delete user reservations across date ranges (max 31 days) by uid, externalId, or email

Check if reservations or parking setup changed since a given unix timestamp

GET STARTED

Start building with Parkalot API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Parkalot API for, with concrete tasks.

★ Automated Reservation Management

Integrate Parkalot reservations into an office management or visitor scheduling system. PUT /reservations/{facilityId} accepts a batch array where each entry specifies spot, day, shifts, and uid (null to unreserve). Use externalId or email to map users between systems, and withWaitlist to trigger automatic assignment when spots free up.

PUT /reservations/{facilityId} with an array of PublicReserveRequest objects. Set uid to the user identifier to reserve, or null to unreserve. Check the ReserveResponse array for per-request success or error.

Real-Time Reservation Monitoring

Poll for reservation changes to drive real-time dashboards or notification workflows. GET /reservations/{facilityId}/did-change/{fromDay}/{toDay}?since={timestamp} returns hasChanges and per-day change flags, allowing efficient incremental syncs without fetching full data when nothing changed.

GET /reservations/{facilityId}/did-change/{fromDay}/{toDay}?since={lastSyncTimestamp} and only re-fetch reservations if hasChanges is true or a specific day's changed flag is set.

Occupancy Reporting

Generate parking occupancy reports for compliance, billing, or analytics by querying the reports endpoint. GET /reports/{facilityId}/readable/{fromDay}/{toDay} returns item-level records with user assignments, reservation/release timestamps, and owner information. Use for weekly summaries, chargebacks, or identifying underutilized spots.

GET /reports/{facilityId}/readable/{fromDay}/{toDay} and parse the items array. Each ItemState record includes item name, user name, reserved_at, released_at, and group membership.

Key Endpoints

5 endpoints — parkalot api provides parking reservation management and reporting for facilities, enabling operators to query reservations in flat or nested formats, create and release parking spot reservations in batch, delete reservations for date ranges, track reservation changes via timestamp comparison, and retrieve parking reports with item-level occupancy details.

METHOD

PATH

DESCRIPTION

GET

/reservations/{facilityId}/nested-day/{fromDay}/{toDay}

Query reservations in nested format grouped by day and item

GET

/reservations/{facilityId}/flat/{fromDay}/{toDay}

Query reservations in flat format with one time period per record

PUT

/reservations/{facilityId}

Create or release parking spot reservations in batch

DELETE

/reservations/{facilityId}/{fromDay}/{toDay}

Delete user reservations for a date range

GET

/reports/{facilityId}/readable/{fromDay}/{toDay}

Retrieve parking occupancy reports

GET

/reservations/{facilityId}/nested-day/{fromDay}/{toDay}

Query reservations in nested format grouped by day and item

GET

/reservations/{facilityId}/flat/{fromDay}/{toDay}

Query reservations in flat format with one time period per record

PUT

/reservations/{facilityId}

Create or release parking spot reservations in batch

DELETE

/reservations/{facilityId}/{fromDay}/{toDay}

Delete user reservations for a date range

GET

/reports/{facilityId}/readable/{fromDay}/{toDay}

Retrieve parking occupancy reports

Why Jentic?

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

Setup

Wiring the Parkalot API by hand means carrying its scoped x-api-key header, shaping the per-facility reservation and report routes, and handling retries yourself. Through Jentic you install once, import Parkalot from the API Directory, store the key once, and your agent calls it.

Permission scoping

Parkalot puts the facility id in the URL path (/reservations/{facilityId}/...), so a rule can pin your agent to one facility: it can read reservations and occupancy reports there. You choose the operations it may call, so destructive ones like reservation deletion are not included unless you add them.

Credential isolation

Your Parkalot API key is stored once, encrypted, by your own Jentic One instance and injected as the x-api-key header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'update reservations for a facility' or 'get a parking occupancy report', and Jentic returns the matching Parkalot operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Parkalot API through Jentic.

What authentication does the Parkalot API use?

The API uses API key authentication via the x-api-key header with scoped permissions: reports-exact-read, reservations-read, reservations-write, users-read, users-write, setup-read, setup-write, spots-read, spots-write, access-write, confirmation-settings-read/write, and integrations-settings-read/write. Jentic stores the key encrypted and injects it at execution time.

What is the maximum date range for reservations?

Reservation queries and deletions support a maximum 31-day range between fromDay and toDay. The API returns 400 Bad Request if the range exceeds this limit.

Can I trigger waitlist processing when releasing a spot?

Yes. Set withWaitlist=true in the PublicReserveRequest or as a query parameter on DELETE operations. This triggers automatic assignment from the waitlist when a spot becomes available.

How do I check for reservation changes without fetching all data?

Use GET /reservations/{facilityId}/did-change/{fromDay}/{toDay}?since={unixTimestampInMillis}. It returns hasChanges and a per-day array of change flags, allowing incremental syncs.

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

Yes. Because you run Jentic One yourself, your own rules decide which Parkalot operations and credentials the agent can use. Since the facility id lives in the URL path (/reservations/{facilityId}/...), you can pin the agent to a single facility and grant only the operations you want, such as reading reservations in nested or flat format and pulling occupancy reports. Destructive calls like deleting reservations for a date range are left out unless you explicitly add them, and the scoped x-api-key stays with your instance rather than the agent's prompt.

Parkalot API

Name: Parkalot API
Brand: Parkalot API
Availability: InStock

Official vendor OpenAPI document · agent-readyMaps GeolocationPlaces SearchapiKey5 EndpointsREST

For Agents

Manage parking spot reservations, track changes, and retrieve occupancy reports for Parkalot parking facilities.

Use for: I need to reserve a parking spot for a user next week, Check if any reservations changed in the last hour, Get a report of all parking occupancy for today, Release all reservations for a specific user

Not supported: Does not control physical access gates, process payments, or manage facility setup - use only for reservation queries, batch reservation updates, deletion, change detection, and occupancy reporting.

Parkalot API provides parking reservation management and reporting for facilities, enabling operators to query reservations in flat or nested formats, create and release parking spot reservations in batch, delete reservations for date ranges, track reservation changes via timestamp comparison, and retrieve parking reports with item-level occupancy details. Authentication uses a scoped API key with permissions for reports, reservations, users, and setup operations.

Jentic One on Github View OpenAPI Document