> ## Documentation Index
> Fetch the complete documentation index at: https://developer.easyparkgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Real time parking transactions webhook

> **CameraPark Fleet only.** This feature is purpose-built for the CameraPark Fleet product. For general access to the same data, use the Billing Info Records feature.

This 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.




## OpenAPI

````yaml webhook parkingTransaction
openapi: 3.1.0
info:
  title: Partner API
  description: >
    The Partner API provides a suite of endpoints designed to help partners and
    customers to manage users, vehicles and billing records seamlessly.

    Note: These endpoints are currently available in Europe, with expansion to
    new regions planned for 2026.


    ## Getting started & onboarding


    To begin integrating with our endpoints, you will need access to our
    environments. Please follow these steps:
      1. Request access: Contact us at api-developer-portal@arrive.com or reach out to your designated point of contact.
      1. Testing & Staging: Once registered, you will be provided with credentials for our Staging environment. This allows you to test your integration end-to-end in a safe, isolated environment.
      1. Production: After successful testing in Staging, your point of contact will guide you through the promotion to the Production environment.

    Requests and responses are in JSON format.


    ## Request timeout


    All the endpoints have a default timeout of 60 seconds.


    ## Errors


    All errors match the standard response for errors as defined by the Problem
    Details for HTTP APIs specification <a
    href="https://datatracker.ietf.org/doc/html/rfc9457">RFC 9457</a>:


    ```json
        {
          "type": "https://developer.easyparkgroup.com/openapi/fleet/overview/",
          "title": "Forbidden",
          "status": 403,
          "detail": "Access denied",
          "instance": "/api/billing-accounts",
          "timestamp": 1771232045624,
          "traceId": "55a47f36-cea3-4b01-92b6-8295c02ac302"
        }
    ```
  version: '2026.01'
servers:
  - url: https://fleet.staging.ezprk.dev
    description: Staging
  - url: https://fleet.europe.ezprk.net
    description: Production
security: []
tags:
  - name: Billing Accounts
    description: Query Billing Accounts and their Billing Info Records.
  - name: Login
    description: Authenticate with the EasyPark API
  - name: Cars allowlist
    description: >
      Cars allowlist allows partners and customers to manage which vehicles are
      permitted to park under an account. By maintaining an allowlist of
      approved vehicles, you ensure that only authorized cars can be associated
      with a fleet.


      ## Two allowlist modes


      The API functionality supports two modes, and the right one depends on how
      your integration is structured:


      **Global allowlist** — A single allowlist applies across all customers
      connected to your integration. Any vehicle added to the allowlist is
      permitted for all customers under that integration. Use this if you manage
      a unified fleet and want one centralized list of approved vehicles.


      **Single Billing Account allowlist** — Each customer connected to your
      integration has their own individual allowlist. Vehicles must be added per
      customer, and a vehicle permitted for one customer is not automatically
      permitted for others. Use this if you manage multiple customers with
      distinct fleets that should remain separated.


      If you are unsure which mode applies to your integration, check with the
      team that set up your API access — the mode is defined at the integration
      level.
paths: {}

````