Get API usage
const url = 'https://app.tunnelhq.com/api/v1/usage';const options = {method: 'GET', headers: {'X-API-Key': '<X-API-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://app.tunnelhq.com/api/v1/usage \ --header 'X-API-Key: <X-API-Key>'Requests made this minute, today, and this month (UTC) against the plan’s limits, with 30 days of daily totals and today’s requests per endpoint.
With a workspace key, the counts and limits are the workspace’s (scope: workspace). With
an account-wide key they’re yours across workspaces (scope: user), and the plan and limits
shown are defaults: each request is still limited by the plan of the workspace it reaches.
Need an API key? See Getting an API key.
Authorizations
Section titled “Authorizations”Responses
Section titled “ Responses ”The usage.
object
Requests today (UTC).
Requests this minute.
Requests this calendar month.
The first day of this month.
The last day of this month.
The plan’s name.
The last 30 days, one entry per day, including days with no requests.
object
Today’s requests per endpoint, most used first. Endpoints are named like GET /servers/:id.
object
workspace for a workspace key; user for an account-wide key.
Example
{ "ok": true, "today": 412, "todayLimit": 25000, "perMinute": 3, "perMinuteLimit": 60, "monthlyUsed": 9870, "monthlyLimit": 250000, "periodStart": "2026-09-01", "periodEnd": "2026-09-30", "plan": "Pro", "dailyHistory": [ { "date": "2026-09-24", "count": 388 }, { "date": "2026-09-25", "count": 412 } ], "endpointBreakdown": [ { "endpoint": "GET /servers", "count": 300 }, { "endpoint": "POST /test", "count": 112 } ], "scope": "workspace"}Headers
Section titled “Headers”Requests the workspace’s plan allows per minute.
Requests left in the current minute.
Unix time, in seconds, when the current minute ends.
The API key is missing, wrong, expired, switched off, or no longer valid.
object
The HTTP status, repeated.
What went wrong.
More detail, on some errors.
Seconds to wait, on the 429 for wrong keys.
Examples
{ "error": true, "code": 401, "message": "API key is required. Provide X-API-Key header or Authorization: Bearer <key>"}{ "error": true, "code": 401, "message": "Invalid or expired API key"}{ "error": true, "code": 401, "message": "API key has expired"}{ "error": true, "code": 401, "message": "API key owner account is inactive"}{ "error": true, "code": 401, "message": "This API key's workspace access has been removed"}A usage limit was reached, or this IP address made too many requests with a wrong key.
Usage limits are per workspace and plan: per minute (Retry-After: 60), per day
(Retry-After: 3600), and per month (no Retry-After). They use their own body shape.
An IP address may send 10 wrong keys a minute; one more is allowed every 6 seconds. While
that allowance is used up, every request from the address is refused, even one with a
valid key.
object
Seconds to wait. Absent for the monthly limit.
object
The HTTP status, repeated.
What went wrong.
More detail, on some errors.
Seconds to wait, on the 429 for wrong keys.
Examples
{ "error": "Rate limit exceeded", "message": "Per-minute limit of 60 requests exceeded", "retry_after": 60}{ "error": "Daily limit exceeded", "message": "Daily limit of 25000 requests exceeded", "retry_after": 3600}{ "error": "Monthly limit exceeded", "message": "Monthly limit of 250000 requests exceeded"}{ "error": true, "code": 429, "message": "Too many failed API key attempts from this address. Wait a few seconds and try again.", "retry_after": 6}Headers
Section titled “Headers”Seconds to wait. 60 for the per-minute limit, 3600 for the daily limit, 6 after wrong keys. Absent for the monthly limit.
Something failed on TunnelHQ’s side.
object
The HTTP status, repeated.
What went wrong.
More detail, on some errors.
Seconds to wait, on the 429 for wrong keys.
Example
{ "error": true, "code": 500, "message": "Internal server error"}