Skip to contentSkip to navigation
Hatcel
Developers
2026-10-08API status

Test data

Build against data that never touches real records

A test key works on test data and nothing else, so an integration can be built and broken without going near a real customer.

What a test key sees

ObjectsTo a test key
customers, bookings and ordersTest rows only. A real one is a 404, and every row carries livemode: false
venues, tags, lists, activities, packages and eventsThe same as to any key: there is no test copy
tickets and gift-cardsNothing. These are always real records, so a test key never sees one

What a test key writes - customers, and the tags and lists on them - is test data, and is removed with it.

Live keys before go-live

While a workspace is still in Stripe test mode, a live key sees its test rows too, as the booking pages do. Once the workspace takes real payments, a live key never sees a test row again.

Removing test data

Clear it all at once, from either place. Both remove every customer the workspace's test keys created, and every tag and list membership they added - revoked test keys included. Live data, and anything staff made, is never touched. This cannot be undone.

  • In Hatcel: open a test key in Settings > Developers and choose Remove all test data.
  • From code: DELETE /test-data with a read and write test key. A live key is refused with a 403.
curl -X DELETE "https://api.hatcel.com/test-data" \
  -H "Authorization: Bearer $HATCEL_API_KEY" \
  -H "Hatcel-Version: 2026-10-08"