Skip to content

Account

GET /v1/me
Terminal window
curl -s https://api.tpp.io/v1/me -H "Authorization: Bearer $TOKEN"
{
"id": "0d9e6b1c-...",
"name": "Acme",
"email": "ops@acme.com",
"role": "customer",
"status": "active",
"pool_bytes": 1000000000,
"used_bytes": 12582912,
"remaining_bytes": 987417088,
"allocated_bytes": 987417088,
"unallocated_bytes": 0,
"logins": 1,
"allow_ips": [],
"created_at": "2026-07-01T09:30:00Z"
}

Your proxy credentials live on your proxy logins, not on the account.

Field Meaning
pool_bytes Total bandwidth ever purchased
used_bytes Spent in total, across all your logins
remaining_bytes Left in total, including what’s allocated to logins
allocated_bytes Handed to proxy logins
unallocated_bytes Not yet handed to any login; what you can still allocate
allow_ips Addresses you may connect from; empty is anywhere
PATCH /v1/customers/{id}

Use your own id from /v1/me. Any subset of:

{
"name": "Acme GmbH",
"email": "billing@acme.com",
"password": "new dashboard password",
"allow_ips": ["203.0.113.7", "198.51.100.0/24"]
}

Returns the updated account. Proxy credentials are changed on the login instead. Balance changes go through your account manager; status is set by us.

allow_ips is the addresses your proxy logins and API keys may be used from - single addresses or CIDR ranges, IPv4 or IPv6, up to 64 entries. Sending the field replaces the whole list; [] clears it and allows anywhere again.

Terminal window
curl -s -X PATCH https://api.tpp.io/v1/customers/$ID \
-H "Authorization: Bearer $TOKEN" \
-d '{"allow_ips": ["203.0.113.7", "198.51.100.0/24"]}'

It covers every proxy login and your API keys - the rule is on the account, so there is nothing to repeat per login. Changes reach the gateways within a few seconds; connections already open are left alone.

Signing in to the dashboard with your email and password is deliberately not restricted, so a wrong entry can always be corrected. GET /v1/ip returns the address you are calling from if you need to check it.