gamexo developersHudle
Coming soon. Registered as a platform, not yet built — we are waiting on Hudle's integration spec.
Coming soon — not yet available
Hudle is a platform gamexo knows about, but the integration is not built. There are no endpoints, and no API key can be issued for it. Attempting to create one is refused rather than quietly producing a key that cannot answer.
What exists today
Hudle appears in a venue's integrations screen as a platform we are working towards, so a venue can see it is coming. That is the whole of it. Nothing guesses at field names or endpoint paths: an invented contract would be worse than an empty one, because it would look finished.
What is blocking it
Hudle's published integration contract. Once we have it, building the adapter is one module — the wire format, and nothing else.
Everything underneath is already written and already running for Playo: availability, holds, atomic multi-slot writes, idempotent retries, 15-minute expiry, per-venue scoping, and an eight-scenario consistency suite. A new adapter inherits all of it without reimplementing any of it, which is why the estimate is short once the spec lands.
In the meantime
If Hudle can call our contract rather than dictating one, no waiting is needed. The gamexo API is live today and a venue can issue a key for it now.
gamexo API
The default contract. Available immediately, no adapter required.
Playo
A worked example of a platform-dictated contract.
For the Hudle team
If you are reading this to scope an integration, what we need from you is:
- The endpoints you expect the venue to host, with paths and methods.
- Request and response bodies, including how you signal a business refusal versus a transport fault.
- How times are expressed — offset, venue-local, or UTC — and how date and time are split, if they are.
- The identifier you will send that is stable across your own retries. That value becomes the idempotency key, and it is what stops a dropped response from double-selling a court.
- Whether you want a two-phase hold-then-confirm flow, or single-phase confirmed bookings.
Send that to your gamexo contact and the adapter follows.