Developers
A public REST API for clubs and certified partners: scoped reads, bookings by API, and HMAC-signed webhooks.
Authentication
Every key is generated from the club panel, under Administration → API & webhooks, and travels as a Bearer header.
curl -H "Authorization: Bearer mp_…" \
https://api.meetandplay.mx/api/v1/clubs/{clubId}/bookingsThe full key is only shown once. Store it somewhere safe.
Endpoints
Every key declares the scopes it was created with; a request without the required scope is refused.
- GET
/clubs/{clubId}/courtsThe club's court catalogue.
- GET
/clubs/{clubId}/availabilityBusy slots per court, up to 14 days.
- GET
/clubs/{clubId}/bookingsThe club's bookings, newest first.
- GET
/clubs/{clubId}/customersThe club's customer directory — personal data, behind its own scope.
- POST
/clubs/{clubId}/bookingsCreates a booking, same as the club's own desk.
- POST
/clubs/{clubId}/bookings/{bookingId}/cancelCancels a booking; refunds or voids the payment per the club's policy.
Webhooks
Receive HMAC-SHA256 signed events at your own URL: booking created, confirmed or cancelled, payment succeeded, and match filled. Every delivery retries with backoff; after several failed attempts it lands in the dead-letter queue, redeliverable from the club panel.
Webhook authentication
On top of the HMAC signature (x-map-signature), each webhook can send an Authorization header, either Basic (username and password) or Bearer (token). Set it up in the club panel, under Administration → API & webhooks, in each webhook's authentication. The credential is stored encrypted and never shown again.
POST https://…/webhooks x-map-signature: t=1767225600,v1=… x-map-delivery: 0199… Authorization: Bearer …
- It is sent on every delivery, including retries and redeliveries from the dead-letter queue, using the credential current at send time: if you change or remove it, the change also applies to deliveries already queued. If the server cannot decrypt the credential, the delivery is never sent without it; it goes to the dead-letter queue. If you change the URL or delete the webhook, deliveries queued for the old URL are cancelled or moved to the dead-letter queue: the credential is never sent to a URL you no longer have registered.
- We still recommend verifying the HMAC signature: the Authorization header says who is calling, but only the signature proves the body was not altered, and its timestamp (t=) lets you reject replayed deliveries.
- Redirects are not followed: a 3xx response counts as a failed delivery and is retried, so the credential never travels to another URL. Register your receiver's final URL.
Rate limits
Every key has a per-minute request cap. A 429 response means it was reached; slow down and retry.
Certified partners
A certified partner connects in one click from the club panel — no keys copied and pasted by hand.
Ready to integrate your club?
Sign in to the club panel and mint your first key under Administration → API & webhooks.
