FAQ

Straight answers on API keys, rate limits, data ownership and export, message storage, send speed, tenant isolation, and account safety.

Common questions about working with the TEASE API, grouped roughly by topic: keys and security, limits, your data, and account safety. Each answer links to the page with the full detail.

Still stuck? The Essentials pages cover auth, response shapes, and limits in depth, and the API Reference documents every endpoint field by field.

Glossary

One word, one meaning. Terms used by more than one service, and the three different things "platform" can mean.

Security

How TEASE protects your fan data and your live account access — plain-English, result-level, and honest about what's live versus what's on the roadmap.

FAQ

What happens if my API key leaks?

How do I rotate a key with no downtime?

What's the difference between read, write, and automation keys?

I'm getting 429s — what should I do?

Who owns my data, and can I export it?

Do you store my fans' message contents?

Can I send broadcasts or DMs faster?

Can another account ever see or touch my data?

Is there a sandbox or test key?

How does TEASE keep my connected account safe?

Why do some reads return 400 before I connect my account?

How do I troubleshoot a non-2xx status?

How do media uploads and cover images work?

Are there plan or billing limits on the API?

Does the API support multiple languages or locales?

Where do I get the OpenAPI spec or an SDK?