Documentation Index
Fetch the complete documentation index at: https://docs.tented.ai/llms.txt
Use this file to discover all available pages before exploring further.
How Authentication Works
The Tented Vibe Coding API uses bearer API keys. Each key belongs to exactly one Tented workspace, and every request runs in that workspace’s context. Send your key in theAuthorization header:
Creating an API Key
Vibe Coding API keys are created inside Tented by a workspace admin.- Ask an admin to create an API key for your workspace.
- Copy the raw key when it is shown.
- Store it in your secrets manager or environment variables.
Request Example
Common Authentication Failures
| Status | Cause |
|---|---|
401 Unauthorized | Missing Authorization header |
401 Unauthorized | Header is not in Bearer <token> format |
401 Unauthorized | API key is unknown, revoked, or expired |
Security Notes
- Treat the key like a password.
- Never expose it in browser-side code.
- Rotate or revoke it if you suspect leakage.
- Use separate keys for separate systems when you want cleaner auditability.
Workspace Scope
An API key cannot cross workspace boundaries. For example:- A tent created with Workspace A’s key cannot be fetched with Workspace B’s key.
- An asset uploaded with one workspace’s key cannot be attached from another workspace.
Required Headers
| Header | Required | Notes |
|---|---|---|
Authorization | Yes | Bearer <api-key> |
Content-Type | Yes for JSON requests | Use application/json for tent and contact write endpoints |
Content-Type | Yes for asset uploads | Use multipart/form-data for POST /v1/tents/{tentId}/assets |
Next: Upload Assets
Learn how to attach files to a new or existing tent before generation.