# ATC Access Request Checklist

## Goal
- Get the minimum real access Ballbox needs to test whether ATC can support the chosen workflow wedge.

## Minimum Ask
- One `client_id`
- One credentialed test account
- Confirmation of supported auth flow for Ballbox use
- Confirmation of target environment: beta or production
- At least one test sportclub with courts and safe data

## Useful Extra Ask
- Permission details for read vs write endpoints
- Whether booking create/update/cancel is allowed in beta
- Any rate limits or environment caveats
- Any webhook/event support for booking changes
- Recommended endpoints for court availability lookup

## Suggested Questions To ATC
- Which auth flow should an external partner actually use?
- What credentials should we use to access beta safely?
- Which endpoints are stable enough for early partner testing?
- Which sportclubs/courts can we use as test data?
- Are there any restrictions on booking writes or participant updates?
- Is there a preferred way to read availability vs bookings vs booking instances?

## Success Condition
- Ballbox can make authenticated calls against a safe environment and inspect real club/court/availability data.