Skip to main content
Get a Tenbyte CDN distribution serving traffic in under 10 minutes. This guide covers the console flow plus the curl checks and API calls that let you automate the rest.

​
Prerequisites

  • A Tenbyte account — Sign up
  • An origin URL that responds to HTTPS (your website, S3 bucket, or custom server)
  • An API token if you plan to script things — generate one in Organization → API Keys
  • curl (bundled with macOS / Linux / WSL)

​
Architecture at a glance

​
1. Open the CDN workspace

Sign in, then pick CDN from the left sidebar.
Tenbyte Dashboard
CDN Dashboard
The CDN workspace lists your distributions.
CDN Distribution

​
2. Create a distribution

Walk through Create distribution to point at your origin. Once active, the console shows a distribution hostname like your-distribution.tenbytecdn.com. Save it to your shell so the snippets below work as-is: 
export CDN_HOST="https://your-distribution.tenbytecdn.com"
export CDN_PATH="/index.html"

​
3. Verify the edge with curl

First request — expect MISS (origin fetch): 
curl -sSI "$CDN_HOST$CDN_PATH" | grep -iE 'http/|x-cache|cache-control|server'
Second request — expect HIT (served from cache): 
curl -sSI "$CDN_HOST$CDN_PATH" | grep -iE 'http/|x-cache'
# HTTP/2 200
# x-cache: HIT
If you see MISS repeatedly, jump to Cache rules — the origin is probably sending Cache-Control: no-store or private.

​
4. Add cache, header, and access rules

GoalWhere
Override TTLs per pathCache rules
Add CORS / security headersHeaders
Geo-block, IP-allow, or referrer-lockAccess rules
Sign URLs for paid / private contentToken authentication
Issue an SSL certSSL

​
5. Automate via the API

All console operations also live in the CDN API. Drop these into CI/CD or a deploy script. 
export TENBYTE_API_TOKEN="..."   # from Organization → API Keys
export DISTRIBUTION_ID="..."     # from the distribution detail page
Purge a path after a deploy: 
curl -X POST "https://api.tenbyte.io/cdn/distributions/$DISTRIBUTION_ID/purge" \
  -H "Authorization: Bearer $TENBYTE_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"paths": ["/index.html", "/static/*"]}'
Inspect the distribution config: 
curl -sS "https://api.tenbyte.io/cdn/distributions/$DISTRIBUTION_ID" \
  -H "Authorization: Bearer $TENBYTE_API_TOKEN" | jq
Endpoint paths shown here mirror the CDN API reference. Always check the reference for the exact shape — it is the source of truth.

​
What “done” looks like

  • curl -I returns HTTP/2 200 from the distribution hostname.
  • Repeat requests show x-cache: HIT.
  • DNS for your custom domain (if any) points at the distribution CNAME.
  • SSL certificate is Active in the console.
  • You can purge a path via the API and watch the next request return MISS.

​
Next steps