Authentication

​

API Keys

​

Key Format

• tb_live_* - Production keys
• tb_test_* - Test/development keys

​

Using API Keys

curl -X POST https://timberlogs-ingest.enaboapps.workers.dev/v1/logs \
  -H "Authorization: Bearer tb_live_xxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"logs": [...]}'

curl -X POST https://timberlogs-ingest.enaboapps.workers.dev/v1/logs \
  -H "X-API-Key: tb_live_xxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"logs": [...]}'

​

Creating API Keys

1. Sign in to app.timberlogs.dev
2. Select your workspace
3. Navigate to Settings > API Keys
4. Click Create API Key
5. Store the key securely - it’s only shown once

​

Key Security

• Keys are hashed before storage (we never store the raw key)
• Use environment variables to store keys in your applications
• Rotate keys periodically
• Revoke compromised keys immediately

​

Error Responses

​

401 Unauthorized

{
  "error": "Missing API key"
}

{
  "error": "Invalid API key"
}

{
  "error": "API key has been revoked"
}

{
  "error": "API key has expired"
}

​

403 Forbidden

{
  "error": "Access denied to workspace"
}

{
  "error": "User has no workspace"
}

​

404 Not Found

{
  "error": "Workspace not found"
}

​

Best Practices

1. Store keys securely - Never commit API keys to version control
2. Use different keys per environment - Separate test and production keys
3. Rotate keys regularly - Especially after team changes
4. Revoke compromised keys immediately - Generate a new key in the dashboard