Test keys (pk_test_) let you build and test against real data without side effects.

What test keys do

Read real clubs, coaches, events, availability, destinations and learning content, exactly like live keys.
Check bookings fully: the club, the slot, the court and the guest details are validated as for a live booking.
Answer a booking with a reference starting TEST, livemode: false and no guest_url.

What they do not do

Store bookings, hold courts, email guests or earn commission.
Let you look a test booking up: GET /bookings/TEST... answers 404 test_booking.
Send booking webhooks. Use Send test on the dashboard to get a signed ping event instead.

Test keys count against your allowance like live keys, so a test suite that calls the API in a loop can use it up. Mock the API in unit tests and keep real calls for a few integration tests.

Testing errors on purpose

To see	Do this
`missing_key`	Call without the `Authorization` header
`invalid_key`	Send `pk_test_` and 40 made-up characters
`validation_failed`	Send `per_page=500`
`club_not_found`	`GET /clubs/no-such-club`
`date_out_of_range`	Availability for a date in the past
`slot_taken`	Book the same test slot as a live booking that exists
`rate_limited`	Make more calls in a minute than your plan allows
`quota_exceeded`	Use up the sandbox allowance

Before you go live

Choose a paid plan and turn on two-factor sign-in.
Create a live key with a clear name and store it as a secret.
Add a webhook endpoint and check your signature code with a test event.
Make sure every place you show data shows its attribution notices.
Make sure you retry only what is safe, with an Idempotency-Key on bookings.
Read the API terms and the acceptable use policy.

Testa med testnycklar | Utvecklarcenter