😎parkdot API documentation

Here is our Dev friendly API documentation.

Base URL

https://parkdot.app/api/v1

Authentication

All API requests require authentication using API Key and Secret headers:

X-API-Key: your-api-key
X-API-Secret: your-api-secret

Generating API Keys

1

Log in

Log in to your Parkdot account.

2

Open API Access

Navigate to Settings → API Access.

3

Select scope

Select scope (READ or WRITE).

4

Generate key

Click "Generate key".

5

Copy credentials

Copy both the key and secret (secret is shown only once).

API Scopes

  • READ: Allows GET requests and exports

  • WRITE: Allows POST, PATCH, DELETE requests

Rate Limiting

Rate limits are based on your organization's plan:

Plan
Rate Limit

Starter

50 requests/minute

Scale

100 requests/minute (custom)

Enterprise

500+ requests/minute (custom)

Rate limit headers are included in every response:

Error Responses

All errors return JSON with a machine-readable code:

Common Error Codes

Code
HTTP Status
Description

VALIDATION_ERROR

400

Invalid request parameters

UNAUTHORIZED

401

Missing or invalid credentials

FORBIDDEN

403

Insufficient permissions

ENTITY_NOT_FOUND

404

Entity not found

SPOT_NOT_FOUND

404

Parking spot not found

BOOKING_NOT_FOUND

404

Booking not found

SPOT_CONFLICT

409

Spot not available

BOOKING_CONFLICT

409

Booking time conflict

RATE_LIMIT_EXCEEDED

429

Too many requests

INTERNAL_ERROR

500

Server error

Entities

List All Entities

Response:

Get Entity Details

Response:

Create Entity

Requires: WRITE scope, ORG_ADMIN role

Lot Creation Schema Format:

  • F(<label>) - Floor label

  • S<label> - Segment label

  • L<count> - Number of lots

Example: F(-1):SA:L10,SB:L23 creates:

  • Floor "-1"

  • Segment "A" with 10 lots (1-10)

  • Segment "B" with 23 lots (1-23)

Response:

Delete Entity

Requires: WRITE scope, ORG_ADMIN role

Response:

Availability

Get Availability Summary

Parameters:

  • from - Start date (ISO 8601 format)

  • to - End date (ISO 8601 format)

Response:

Get Spot Availability Timeline

Response:

Spots

List Spots

Query Parameters:

  • floor (optional) - Filter by floor label

  • segment (optional) - Filter by segment label

  • availableAt (optional) - Filter only available spots at date

Response:

Booking

Book a Lot (Auto-assign)

Requires: WRITE scope

Automatically assigns the first available spot in the entity for the requested period.

Response:

Edit Booking

Requires: WRITE scope

Response:

Get Booking Info by Plate

Parameters:

  • plate (required) - Vehicle plate number

  • at (optional) - Check at specific date/time (defaults to now)

Response:

Exports

Export Entity Availability

Response: Excel file (XLSX) with availability data per day

Export Spot Availability

Response: Excel file (XLSX) with spot availability timeline

Examples

List Entities

Get Availability Summary

Book a Parking Spot

Get Booking by Plate

Best Practices

1

Store credentials securely

Never commit API keys to version control.

2

Use HTTPS

All requests must use HTTPS.

3

Handle rate limits

Implement exponential backoff.

4

Validate dates

Use ISO 8601 format (UTC recommended).

5

Check responses

Always check the code field for error handling.

6

Monitor usage

Track your API usage in Settings.

Support

  • Email: support@parkdot.app

  • Documentation: https://parkdot.app/api/docs

  • Status: https://status.parkdot.app (future)

Last updated