Get Billing Accounts - EasyPark Developer Portal

GET

/

api

/

billing-accounts

Get Billing Accounts

curl --request GET \
  --url https://fleet.staging.ezprk.dev/api/billing-accounts \
  --header 'Authorization: Bearer <token>'

[
  {
    "baId": 123,
    "crn": "<string>",
    "customerName": "<string>",
    "departmentName": "<string>"
  }
]

Authorizations

Authorization

string

header

required

You can get the JWT from the Login endpoint

Response

Returns the billing accounts associated with the authenticated company

baId

integer<int64>

Billing account ID

crn

string

Company registration number

customerName

string

Customer name

departmentName

string

Department name

Real time parking transactions webhookThis defines the contract for the webhook payload that EasyPark sends to partners. It is intended for partners implementing a receiver endpoint. EasyPark transmits this webhook payload to your registered endpoint immediately upon the completion of a paid parking session. Authentication is configured per partner and supports two modes: - **HTTP Basic Auth**: EasyPark Fleet sets the `Authorization` header with a `Basic <base64(username:password)>` value. - **API key**: EasyPark Fleet sets a custom header (name configured per partner) with an API key value. ## Errors Failed parking transaction posts (HTTP 4XX or 5XX), excluding 409 Conflict duplicate records, will be retried hourly until accepted by the partner. If a duplicate record is identified by the partner, we expect the partner system to return a [409 Conflict](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/409); these transactions are treated as successfully processed and will not be retried.

⌘I

Get Billing Accounts

curl --request GET \
  --url https://fleet.staging.ezprk.dev/api/billing-accounts \
  --header 'Authorization: Bearer <token>'

[
  {
    "baId": 123,
    "crn": "<string>",
    "customerName": "<string>",
    "departmentName": "<string>"
  }
]