Skip to content
PL

Profiles and IP-list API

Methods for configuring protection and address lists.

Profiles

Method Path Role
GET / POST /v1/orgs/{org}/profiles member / admin
GET / PUT / DELETE /v1/orgs/{org}/profiles/{id} member / admin / admin

Profile fields include name, limbo, level, verifiedTtlSec, verifiedMaxUses, securityChecks, packetOrder, ipList, rateLimit, cps, maxPerIp, version, minVersion, antiVpn and motd.

Configure a profile in the panel first, then retrieve its data as an integration starting point. Parameters depend on verification mode; invalid combinations return validation. Do not present managed-profile settings as editable fields.

PUT replaces the full configuration. A profile referenced by a route cannot be deleted (409 in_use). Free-plan restrictions apply through the API (403 plan_restricted).

IP lists

Method Path Role
GET / POST /v1/orgs/{org}/iplists member / admin
GET / PUT / DELETE /v1/orgs/{org}/iplists/{id} member / admin / admin

Example create or update body:

{
  "name": "Blocked addresses",
  "entries": [{"cidr": "192.0.2.0/24", "action": "deny"}]
}

This is a reserved documentation range. Each entry has cidr and action (allow or deny). Saving a list does not attach it to a route: use the route's ipListIds field. Referenced lists cannot be deleted.