Tessera DocsConnecting sources
0%

API reference

4 min read

Authentication

Authenticate every request with a secret key, scope keys to the right environment, and learn which errors mean a key is missing or revoked.

Every request to the Tessera API is authenticated with a secret key sent in the Authorization header. Requests without a valid key return 401 Unauthorized.

terminal

curl https://api.tessera.dev/v1/events \ -H "Authorization: Bearer $TESSERA_KEY"

Key scopes

Keys are scoped to a single workspace. Create separate keys for each environment so you can rotate one without touching the others.

  • Write keys can send events but can’t read data

  • Read keys can query events and schemas

  • Admin keys can manage sources, destinations and members

Keep keys server-side

Secret keys grant access to your workspace. Never ship them in browser or mobile code. Use a write key behind your own endpoint instead.

Was this page helpful?

Most searched

The three articles developers open most. Start here if you're stuck on auth, webhooks or keys.

Support

Docs answer most questions. For everything else, the engineers who built the API are one message away.

MK

Maya · Northwind

Our webhooks stopped at 14:02 UTC. Request ID req_8f2a91.

PS

Priya · Tessera engineer

Found it. Your endpoint returned 502 for 3 minutes. We replayed 214 events, all delivered.

Priya is typing

CAN’T FIND IT?

Ask the people who build the API. Send a request ID

or a failing payload and we’ll trace it on our side.

Replies in under 4 hours on weekdays

Answered by engineers, not a script

Full logs checked for every request ID

Quire Template

from

$79

Quire template preview

Create a free website with Framer, the website builder loved by startups, designers and agencies.