Skip to content
Ezaz Developers

Sell padel courts in your app, in real time

Ezaz runs the courts, desk and bookings of padel venues across Egypt. Its partner API lets booking apps such as Kabten, Padel Place or Spark show a venue's free courts and book them for their players. Every booking lands on the venue's desk at once, with no double booking.

What the API does

  • Lists the venues that let you sell their courts, with each court's facts, photos, rating and safety summary.
  • Shows each court's free slots and prices on a Cairo date (60, 90 or 120 minutes, from any half hour).
  • Books and cancels courts for your players, safely retried with an idempotency key and tied to your own reference.
  • Shows a player's packages and memberships at a venue, so they can pay with package minutes.
  • Lets your players review a court after they played, and tells you when the venue replies.
  • Lets your players report a safety problem on a court, with photos, and tells you when the venue resolves it.
  • Tells your server about every change through signed webhooks.

The rules, in plain words

These come from the venues and from Egyptian law. The API enforces them; your app should explain them to players.

Ezaz never holds player money

Each booking says how it is paid: PAY_AT_VENUE (the player pays at the venue's desk; their membership discount applies), PREPAID_BY_PARTNER (you took the money in your app, send what you collected, and settle the court price with the venue: it shows on the venue's partner statement), or PACKAGE (minutes from the player's package at that venue, given back if the booking is cancelled). A package pays only when you set customer.phoneVerified to true: your word that the player proved that phone to you, for example with a one-time code. Ezaz records it with the booking.

The venue sees the player's name and phone

Players have no Ezaz account: they are yours. With each booking you send the player's name and the mobile number you verified, in E.164 (+201001234567). The venue sees both on the booking and in its customer list, so tell your players that the venue receives their name and number. Ezaz processes this data for you under a data processing agreement (Egypt's PDPL, Law 151/2020).

Only venues that chose you

A venue decides which apps may sell its courts. You see only active venues that granted your app, and only your own reservations, reviews and reports; anything else answers 404.

Reviews come from the app that booked

Only the partner that made a reservation can review it, after it was played, within 14 days of its end, and once. Sending the same review again returns it; a different one is refused.

Cancelling follows the venue's cutoff

You can cancel free of charge until the venue's cancellation cutoff (cancellationHours on each venue). After that, only the venue can cancel.

Safety reports are about the court

A report says what is wrong with the court: never medical details or the names of anyone injured. The venue never learns who reported, and a player can send at most 5 reports a day through you.

How an integration goes

  1. Request access. Ezaz registers your app and gives you a client id and a client secret, shown once.
  2. Your server gets a 10-minute token with the OAuth 2.0 client credentials grant.
  3. Read the venues that granted you, their courts and the free slots.
  4. Book for your player, then keep in sync through webhooks.