> For the complete documentation index, see [llms.txt](https://teeket.gitbook.io/legals/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://teeket.gitbook.io/legals/api-guidelines.md).

# API Guidelines

## teeket API – developer guidelines

hey friend 👋

welcome to the teeket API. this is your quick guide to using it well and keeping everything running smooth.

***

### 🚀 getting started

* grab an **API key** from your dashboard, or the one we shared with you.
* keep that key secret. don’t post it on github or share it in screenshots.
* use your key in the `Authorization` header when making requests.

***

### 📝 what you can do

* fetch events, tickets, and payments data your app is authorized for.
* create experiences around events (search, discovery, analytics, ticketing).
* experiment in a test/sandbox environment before going live.

***

### ⚠️ what you shouldn’t do

* no scraping, spamming, or hitting endpoints you’re not supposed to.
* don’t try to bypass rate limits or reverse engineer the API.
* don’t store or share people’s personal data unless you have their okay.

***

### ⏳ rate limits

* we set rate limits to keep things fair for everyone.
* if you get a `429 Too Many Requests`, back off and retry later.
* if you need higher limits, email us at \[your email].

***

### 🔐 security & privacy

* treat API credentials like passwords.
* encrypt sensitive data in transit and at rest.
* follow privacy laws when handling user data (GDPR, CCPA, etc.).

***

### 🔄 updates

* we’re always improving the API.
* watch the changelog / developer newsletter for updates.
* breaking changes will get advance notice when possible.

***

### 🛟 support

* dev questions? bugs? hit us up at \[<dev-support@teeket.com>].
* include your app name, environment (test/live), and request IDs if you can.

***

### ❤️ community

we want people to build cool stuff.\
if you’re making something public, let us know — we might feature it.\
be kind to the API and to other developers.

#### tl;dr

* keep your keys secret
* respect rate limits
* only grab data you’re allowed to
* handle user info with care
* reach out if you’re stuck

happy building 🚀\
— your friends at teeket