Details about deprecated APIs

Introduction

Autopay offers a range of public APIs. Our goal is to design good and stable APIs, but as Autopay is under constant development, the need for changes is unavoidable. As per Autopay’s API Usage Agreement all breaking changes are published 6 months prior to release.

Notification

Deprecations

Published: 5th of May 2026

Comes into effect: 5th November 2026

API: Booking API

Description of change:

Booking API version 1 and version 2 will be deprecated with this change. For a guide on how to migrate to version 3, please see the Migration guide

Published: 5th of May 2026

Comes into effect: 5th November 2026

API: Fleet API

Description of change:

Fleet API version 1 will be deprecated with this change. Changes in version 2 include:

1. All endpoints should have /fleet/v2/ in the path. Previously, this was only /fleet/
2. Request parameters and responses for license plate changed from plate to license_plate_number

Published: 5th of May 2026

Comes into effect: 5th November 2026

API: Permit Landlord API (Previously known as E-Commerce API)

Description of change:

Old endpoints using camel case will be deprecated with this change. Move to the new endpoints per current API doc. The endpoints that have changed are:

• GET - Get the available permit definitions
• PUT - Create a new permit allocation
• POST - Update permit allocation
• DELETE - Delete permit allocation

Published: 5th of May 2026

Comes into effect: 5th November 2026

API: Statistics API

Description of change:

The legacy field parkings.payments.id will be removed with this change. It has been replaced by the parkings.payments.payment_id field.

Published: 19th of February 2026

Comes into effect: 19th August 2026

API: Accounting API

Description of change:

Receipts and entry/exit images are protected by JWTs just like the API itself. New fields pointing to auth endpoints are already available. The new fields are receipt_url_with_auth and image_url_with_auth