Changelog

Each account may send up to 100 requests a second with a live key, and 25 with a test key. Over the limit, a request fails with HTTP 429 and rate_limited. Tell us if you need more.

A webhook endpoint can now be changed, with a new URL or other events, without removing it. It can send a ping test event, so you can see your server receive one. And it can get a new secret: the old one stops at once, or in 24 hours, with every event signed with both until then.

Test staging areas, the ones a lk_test_ key works on, are made up. No vehicles stand in them, and they are your account's alone. They work just as real ones do.

A staging area's owner can now let vehicles stay as long as they like, as at a lot where they wait out the night. There rules.max_stay_minutes is null, and so is a checked-in reservation's leave_by, unless a closure of its spot is planned.

Where there is a limit, a vehicle past it still gets one reservation.overstayed event. What follows is for the owner to decide.

Getting started is now four pages: getting an API key, your first request, your first reservation, and going live. Anyone can sign up for a test key; a live key comes once we have approved your company.

A staging area now lists the closures its owner has planned, in closures, for some spots or all of them. Nobody is asked to leave for one: leave_by never runs past its start.

A sudden closure, by the police or for a fire, sends every vehicle away. A checked-in vehicle gets the new reservation.must_leave event, with others nearby with room.

The first version of the API docs, written down before it is built: staging areas, availability, reservations and webhooks. Nothing can be called yet.