Retrieve a contact's reward points
The contact's reward points balance at each of the key's locations (points are kept per location), and whether the business runs the reward points program there. A location with no points for this contact answers `balance: 0`. A location-limited key sees only its own locations. Pass `include=history` to also get the latest 50 points changes (earned, spent, given back, adjusted), newest first. A contact that is not in the key's company answers `404`.
Authorization
ApiKeyAuth Send your API key as a bearer token: Authorization: Bearer bp_sk_live_.... Mint and revoke keys in your dashboard under Settings -> Developers.
In: header
Path Parameters
uuidQuery Parameters
history adds the latest 50 points changes at the key's locations.
Value in
- "history"
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/contacts/497f6eca-6276-4993-bfeb-53cbbbba6f08/reward-points"{ "contact_id": "8b0e6a1c-2f4d-4e7a-9c3b-5d1f0a2e7c44", "data": [ { "location_id": "2c7d9e10-4b6a-4f2e-8a1d-0e5c3b7f9a21", "program_enabled": true, "balance": 340, "last_activity_at": "2026-11-12T18:04:11Z" } ], "history": [ { "id": "f4a2c8e1-7b3d-4c9a-a1e6-2d5b8f0c3e77", "location_id": "2c7d9e10-4b6a-4f2e-8a1d-0e5c3b7f9a21", "delta": 40, "reason": "earned", "occurred_at": "2026-11-12T18:04:11Z", "order_id": "9e3b1f6a-0c2d-4a8e-b5f7-1d4c6a8e2b90", "item": "Haircut" } ]}List published reviews
The business's own customer reviews that are published (the same reviews its booking page shows), newest first. Private feedback and hidden reviews are never returned. The reviewer is shown as first name and last initial ("Shev S."): no contact id, full name, email or phone is ever sent. A location-limited key sees only reviews of its own locations. Pass `location_id` to narrow to one of the key's locations, and `technician_id` for the reviews of one staff member.
Register a webhook endpoint
Register an https URL to receive events. Booking Pro POSTs a JSON body for each subscribed event, signed with HMAC-SHA256 in the `X-BookingPro-Signature` header (`sha256=<hex>`) using the `secret` returned here. Verify every delivery by recomputing the HMAC of the raw request body with that secret. Each delivery also carries a unique `X-BookingPro-Event-Id` you can use to deduplicate. The `secret` is shown ONLY in this response. Subscribe to specific event types, or `"*"` for all. Send an `Idempotency-Key` so a retried create does not register twice. The body of every delivery is a `WebhookEvent`; payment events carry `amount_cents`, `tip_cents` and their `currency` (uppercase ISO 4217).