canonical: https://jentic.com/apis/easyparkgroup.com/easypark

# Easyparkgroup EasyPark API

EasyPark is a Europe-wide mobile parking payment platform whose partner API exposes the parking resource catalogue used by EasyPark and its operator partners. The current partner surface lets a partner exchange credentials for an access token, list the parking resources available to the integration, and fetch detail on a single resource. It is used by mobility apps, fleet platforms, and travel planners that need to surface authoritative parking inventory inside their own UX.

## For AI agents

Authenticate against the EasyPark partner API, list available parking resources, and fetch detail on a specific resource for parking-aware applications.

## Scope

Does not handle parking session start, session stop, or payment processing - use for EasyPark partner authentication and parking resource discovery only.

## Capabilities

- Exchange partner credentials for a short-lived access token via the auth endpoint
- List the parking resources available to the partner integration
- Retrieve a specific parking resource's detail for display in a mobility app
- Filter resources to surface only those relevant to a specific mobility partner context

## Use cases

### Mobility app parking discovery

A mobility super-app surfaces parking inventory alongside transit, ride-hail, and rental options. An agent calls `/auth/token` to mint a partner token, then GET /resources to fetch the catalogue and GET `/resources/{id}` for detail when the user taps a tile, all without the user leaving the host app.

Example prompt: Mint an EasyPark access token, then list the first 20 parking resources and return their IDs and names.

### Fleet planning with parking constraints

Fleet platforms that route delivery or service vehicles can call EasyPark's resources endpoint to confirm authorised parking exists at each stop. The detail endpoint returns the metadata the planner needs to honour restrictions before the vehicle leaves the depot.

Example prompt: Given a list of stop IDs, fetch each EasyPark resource detail and return whether the resource is currently active.

### Travel concierge parking lookups

Travel concierge agents can answer questions like 'where can I park near my hotel for the night?' by listing EasyPark resources and filtering on the relevant city or zone. The flow ends with a single resource detail call to surface specific opening hours, rates, or vehicle restrictions.

Example prompt: List EasyPark resources matching a partner-defined city and return the top three with their resource IDs and short descriptions.

### Agent-driven token refresh and discovery

Through Jentic, an agent that needs parking data does not have to manage the token lifecycle manually. Jentic resolves the auth flow, calls `/auth/token` when the cached token has expired, and chains the call to /resources, hiding the multi-step OAuth-style exchange from the user.

Example prompt: Refresh the EasyPark access token if needed, then list the parking resources and return the count.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/token` | Exchange partner credentials for an access token |
| GET | `/resources` | List parking resources |
| GET | `/resources/{id}` | Get a specific parking resource |

## Key resources

- **Authentication** — Exchange partner credentials for a partner access token
- **Resources** — List available parking resources and retrieve resource detail

## Why Jentic

- **Setup:** Wiring EasyPark by hand means exchanging your partner credentials at `/auth/token`, caching the returned access token, and refreshing it before it expires. Through Jentic you install once, import EasyPark from the API Directory, store the partner credentials once, and your agent calls it while Jentic handles the token exchange.
- **Permission scoping:** EasyPark puts the resource id in the URL path (`/resources/{id}`), so a rule can pin your agent to one parking resource: it can read that resource and nothing else. You choose the operations it may call, so it stays limited to discovery reads unless you add more.
- **Credential handling:** Your EasyPark partner credentials are stored once, encrypted, by your own Jentic One instance, which exchanges them for an access token and injects it at execution time. The raw partner secret never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list parking resources', and Jentic returns the matching EasyPark operation with its input schema and its dependency on the auth flow so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **ParkWhiz API** — North American off-street parking inventory and bookings
- **Google Maps Platform** — Geocoding, routing, and place data to anchor parking results
- **HERE Maps API** — Geocoding, routing, and place data that pairs with parking inventory

## FAQ

### What authentication does the EasyPark API use?

Partners exchange credentials at `/auth/token` to receive an access token, then pass it in the Authorization header on subsequent calls. Through Jentic, the partner credentials are stored encrypted in the vault and the token exchange is handled automatically before each request.

### Can I list all available parking resources with the EasyPark API?

Yes. GET /resources returns the parking resources visible to your partner integration. Each entry includes a resource ID that can be passed to GET `/resources/{id}` to fetch the full detail used in app UIs.

### What are the rate limits for the EasyPark API?

The OpenAPI spec does not declare numeric limits. EasyPark applies per-partner contracts, and tokens issued by `/auth/token` are short-lived - refresh them on a schedule to avoid 401 responses, and contact your EasyPark integration manager for plan-specific caps.

### How do I list parking resources through Jentic?

Search Jentic for 'list parking resources', load the schema for GET /resources, then execute. Jentic injects a fresh token from the cached auth/token response. The flow is: pip install jentic, then await client.search, await client.load, await client.execute.

### Does the EasyPark API support starting and stopping parking sessions?

This 3-endpoint partner surface covers authentication and resource discovery only. Session start, stop, and payment flows are part of the broader EasyPark consumer experience and are not exposed by these endpoints.

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

Yes. Because you run Jentic One yourself, your own rules decide which EasyPark operations the agent may call, so you can keep it to discovery reads like GET /resources and GET `/resources/{id}` without granting anything more. Since the resource id sits in the URL path (`/resources/{id}`), a rule can pin the agent to a single parking resource, letting it read that one resource and nothing else. You also control whether it may exchange partner credentials at `/auth/token`, keeping the agent scoped to exactly the calls you approve.